High

CVE-2026-104939 — NGINX Ingress Controller vulnerability

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.

Published Oct 14, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: f5

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.4% (30-day exploitation probability)+4
Technical severity (high)+6
Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.36%

ahead of 28% of scored CVEs · Oct 15, 2026

Affects

Nginx Ingress Controller

CVSS base

7.5

High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (F5 Nginx Ingress Controller).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
F5	Nginx Ingress Controller	≥ 5.6.0 and < 5.7.0	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
8.7	CVSS 4.0	High	—	—	f5sirt@f5.com via NIST National Vulnerability Database
8.7	CVSS 4.0	High	—	—	f5 via CVE Program (cve.org) e CISA ADP
7.5	CVSS 3.1	High	3.9	3.6	f5sirt@f5.com via NIST National Vulnerability Database
7.5	CVSS 3.1	High	—	—	GitHub, Inc. via GitHub Security Advisories
7.5	CVSS 3.1	High	—	—	f5 via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (score shown at the top: f5sirt@f5.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-303

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
SSVC assessment updated
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · Received → Awaiting Analysis
Oct 14, 2026 · NIST National Vulnerability Database
Affected products added · f5/nginx ingress controller
Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 14, 2026
CVSS changed · 7.5
Oct 14, 2026 · NIST National Vulnerability Database
Source status changed · → Received
Oct 14, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 14, 2026 · Alertas do Telegram
CVE published
Oct 14, 2026 · f5

Source activity

Repeated readings are counted rather than listed.

2× References added · Oct 14, 2026 – Oct 15, 2026
1× Official description updated · Oct 14, 2026 – Oct 14, 2026

References

3 on the record

nvd.nist.gov/vuln/detail/CVE-2026-104939
GitHub Security Advisories
github.com/advisories/GHSA-qcp7-h72p-6whw
GitHub Security Advisories
my.f5.com/manage/s/article/K000162617
vendor-advisory, NIST National Vulnerability Database

Elsewhere on this site

F5
every CVE for this vendor

CWE-303
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-94197 NGINX Ingress Controller vulnerability 1d
High CVE-2026-77180 NGINX Ingress Controller vulnerability Sep 2, 2026
High CVE-2026-60005 NGINX ngx_http_slice_module vulnerability Jul 15, 2026
Medium CVE-2026-60065 NGINX Plus ngx_stream_mqtt_filter_module vulnerability Jul 15, 2026
High CVE-2026-55723 NGINX Ingress Controller vulnerability Jul 15, 2026
Medium CVE-2026-56434 NGINX ngx_http_ssi_module vulnerability Jul 15, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-104939 is "NGINX Ingress Controller vulnerability", rated High. It affects Nginx Ingress Controller (F5); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 0.36% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.