Loading vulnerability…
A vulnerability in ingress-nginx allows the nginx.ingress.kubernetes.io/auth-method Ingress annotation to be abused to inject arbitrary NGINX configuration into the generated controller configuration. Successful exploitation can result in arbitrary code execution in the context of the ingress-nginx controller and can also enable disclosure of Kubernetes Secrets that the controller is permitted to access (often cluster-wide Secrets in default installations). Affected ingress-nginx versions are releases prior to v1.13.7 and prior to v1.14.3.
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.
nginx.ingress.kubernetes.io/auth-method annotation (e.g., via a validating admission controller policy rejecting Ingresses containing it). Restrict who can create/modify Ingress resources and annotations (RBAC hardening). Reduce the ingress-nginx controller’s Kubernetes API permissions, especially Secret read access (avoid cluster-wide Secret access; scope to required namespaces). Monitor for suspicious/unauthorized values or changes to the auth-method annotation as potential exploitation attempts.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.
18 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.