Loading vulnerability…
CVE-2026-40246 is an authorization flaw in the UDR service of free5GC affecting version 1.4.2 and earlier. In the handler responsible for deleting Traffic Influence Subscriptions, the code validates whether the influenceId path segment equals the expected value for the deletion endpoint, but when that validation fails it sends an HTTP 404 response and does not terminate execution. Because processing continues after the failed check, the backend deletion logic still executes and removes the targeted subscription. This creates a condition where a request with an invalid influenceId can still delete a Traffic Influence Subscription, while the API misleadingly reports the operation as not found. The issue affects the deletion handler for Traffic Influence Subscription state and enables unauthorized deletion through improper enforcement of request validation and access control logic.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.