Loading vulnerability…
CVE-2024-7646 is a high-severity vulnerability in ingress-nginx in which a user with permission to create Ingress objects in the networking.k8s.io or extensions API groups can bypass annotation validation and inject arbitrary commands into the ingress-nginx controller’s generated configuration. The issue allows malicious annotation content, including carriage-return-based payloads as referenced in the supporting content, to evade validation controls and be interpreted by the controller. Successful exploitation can expose the ingress-nginx controller’s credentials; in the default configuration, those credentials have access to all Kubernetes secrets in the cluster.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A prior ingress-nginx configuration injection vulnerability involving annotation-based injection via carriage return, mentioned as historical context.
A previous ingress-nginx annotation-based injection vulnerability referenced as part of a pattern of configuration injection issues.
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.