Security readout for executives and security teams
Plain-English summary
CVE-2026-1580 affects Kubernetes ingress-nginx. A user who can create or modify Ingress annotations may inject NGINX configuration through the auth-method annotation. The reported impact includes code execution in the ingress-nginx controller context and possible disclosure of Kubernetes Secrets the controller can access.
Executive priority
Treat as high priority for Kubernetes environments using ingress-nginx. The concern is not broad unauthenticated internet exploitation; it is abuse of existing Kubernetes permissions to reach sensitive controller capabilities and Secrets.
Technical view
The issue is improper input handling in the nginx.ingress.kubernetes.io/auth-method annotation, classified as CWE-20. CVSS 3.1 is 8.8: network reachable, low complexity, low privileges required, no user interaction, with high confidentiality, integrity, and availability impact. The record notes default controller access may include all cluster Secrets.
Likely exposure
Clusters using ingress-nginx are relevant, especially where non-admin users, tenants, or automation can create or update Ingress resources. Exposure is higher if the controller has broad Secret access, which the CVE notes is typical in default installations.
Exploitation context
The source bundle does not cite active exploitation, and KEV status is false. Exploitation requires privileges to set or modify an Ingress annotation, but the potential blast radius includes controller-level execution and Secret disclosure.
Researcher notes
Available evidence identifies the vulnerable annotation and impact but does not provide affected version ranges or a named fix in the supplied sources. Avoid assuming exploit availability. Focus assessment on ingress-nginx deployment, annotation control, RBAC boundaries, and Secret exposure.
Mitigation direction
- Check the Kubernetes ingress-nginx issue and vendor guidance for fixed versions or official mitigations.
- Restrict who can create or update Ingress resources and annotations.
- Review ingress-nginx controller permissions, especially cluster-wide Secret access.
- Prioritize upgrades or configuration changes once official guidance identifies them.
Validation and detection
- Inventory clusters running Kubernetes ingress-nginx.
- Identify users, service accounts, and pipelines allowed to modify Ingress objects.
- Search Ingress manifests for nginx.ingress.kubernetes.io/auth-method usage.
- Review ingress-nginx controller RBAC for Secret access scope.
- Monitor the referenced Kubernetes issue for remediation details.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-1580 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/kubernetes/kubernetes/issues/136677CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.