Loading vulnerability…
CVE-2026-1580 is a configuration injection vulnerability in ingress-nginx. The issue arises from unsafe handling of the nginx.ingress.kubernetes.io/auth-method Ingress annotation, which can be abused to inject attacker-controlled configuration into the generated nginx configuration. By supplying crafted annotation content through an Ingress resource, an attacker with the ability to create or modify Ingress objects can cause nginx to process unintended directives. Successful exploitation can result in arbitrary code execution in the security context of the ingress-nginx controller and exposure of Kubernetes Secrets that the controller is permitted to access. In default deployments, this may include Secrets across 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.
nginx.ingress.kubernetes.io/auth-method annotation through a validating admission policy or equivalent admission control. Restrict who can create or modify Ingress resources and annotations through RBAC. Reduce the ingress-nginx controller's permissions, especially access to Kubernetes Secrets, and avoid cluster-wide Secret access where not strictly required. Monitor for unexpected or suspicious changes to Ingress annotations that may indicate 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.