Loading vulnerability…
free5GC UDR contains an improper input validation vulnerability in its EE subscription handling logic. Specifically, the ueId validation performed in HandleCreateEeSubscriptions and HandleQueryeesubscriptions is overly permissive due to a trailing regex branch ('|.+') that accepts any non-empty string. As a result, arbitrary non-3GPP ueId values can be accepted by the UDR SBI endpoint, persisted to storage, and later retrieved. This breaks the expected constraint that stored identifiers conform to supported 3GPP SUPI/GPSI-style formats and can corrupt the integrity of identifier namespaces relied upon by other components.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.