cve.bz

CVE-2026-104939 f5 nginx ingress controller

8.7 highEPSS 0.4%

High (8.7) in f5 nginx ingress controller. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Description NGINX Ingress Controller has a vulnerability when implementing an externalAuth policy for ingress. NGINX Ingress Controller may mishandle the HTTP response from an OAuth IdP and allow an attacker to acquire unauthenticated access to protected paths before the proper external authentication can happen. Impact This vulnerability may allow remote attackers unauthenticated access to protected paths. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-303 Incorrect Implementation of Authentication Algorithm
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-104939 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-104939?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-104939?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-104939 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-104939

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-104939](https://cve.bz/cve/badge/CVE-2026-104939.svg)](https://cve.bz/cve/CVE-2026-104939)

HTML:

<a href="https://cve.bz/cve/CVE-2026-104939"><img src="https://cve.bz/cve/badge/CVE-2026-104939.svg" alt="CVE-2026-104939"></a>

Affected

  • f5:nginx ingress controller

Versions

From the CNA's record in the CVE List.

ProductAffected
F5 NGINX Ingress Controllerfrom 5.6.0 before 5.7.0

Attack patterns (CAPEC)

  • CAPEC-90 Reflection Attack in Authentication Protocol Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON