{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-94197 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-94197 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-94197 is a high-severity authentication bypass vulnerability in F5 NGINX Ingress Controller, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-94197 and fix it if it is affected.\n\nWhat it is: CVE-2026-94197 is a high-severity authentication bypass vulnerability in F5 NGINX Ingress Controller, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-94197 in the wild and no public exploit code.\n\nAffected product: F5 NGINX Ingress Controller. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-94197/ (Markdown: https://insights.sbomify.com/CVE-2026-94197/index.md)","id":"CVE-2026-94197","markdown":"https://insights.sbomify.com/CVE-2026-94197/index.md","name":"CVE-2026-94197","record":{"aliases":["GHSA-5m5m-935w-8wj6"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"NGINX Ingress Controller","requires_auth":"none","summary":"Attackers can bypass authentication in NGINX Ingress Controller by spoofing headers when ExternalAuth is enabled, gaining unauthorized access to protected paths.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"f5","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"An authentication and authorization bypass vulnerability exists in F5 NGINX Kubernetes Ingress Controller (NIC) when configured with the `ExternalAuth` policy or Ingress external authentication. Client-supplied X-Forwarded-Prefix, X-Forwarded-URI, X-Original-URI, and X-Forwarded-Method routing and method headers are forwarded unsanitized into the internal authentication subrequest (handled by the NGINX auth_request directive). As a result, an unauthenticated, remote attacker may spoof request attributes evaluated by the external authentication provider. \n\nImpact:\nThis vulnerability may allow remote attackers \n\nunauthenticated\n\n access to protected \n\npaths. There is no control plane exposure; this is a data plane issue only.\n\nNote: Software versions which have reached End of Technical Support (EoTS) are not evaluated.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"NGINX Ingress Controller vulnerability","id":"CVE-2026-94197","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"TLS 1.3 client ticket store crashed by NewSessionTicket with empty early_data extension in ssl","id":"CVE-2026-94200"},"packages":[],"prev":{"headline":"Other in mint","id":"CVE-2026-94194"},"products":["NGINX Ingress Controller"],"published":"2026-10-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["F5"]},"summary":"Attackers can bypass authentication in NGINX Ingress Controller by spoofing headers when ExternalAuth is enabled, gaining unauthorized access to protected paths.","url":"https://insights.sbomify.com/CVE-2026-94197/"}