{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-55723 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-55723 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-55723 is a high-severity code injection vulnerability in F5 NGINX Ingress Controller, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-55723 and fix it if it is affected.\n\nWhat it is: CVE-2026-55723 is a high-severity code injection vulnerability in F5 NGINX Ingress Controller, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-55723 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-55723/ (Markdown: https://insights.sbomify.com/CVE-2026-55723/index.md)","id":"CVE-2026-55723","markdown":"https://insights.sbomify.com/CVE-2026-55723/index.md","name":"CVE-2026-55723","record":{"aliases":["GHSA-wxxq-mwhh-cvm2"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"NGINX Ingress Controller","requires_auth":"low_privilege","summary":"Authenticated attackers can inject arbitrary NGINX directives via unsanitized CRDs or annotations, potentially executing code or modifying files.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"f5","cpe":[{"product":"nginx_ingress_controller","vendor":"f5"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-76","name":"Improper Neutralization of Equivalent Special Elements"}],"description":"When NGINX Ingress Controller is configured with Custom Resource Definitions (CRDs) or Ingress annotations, an injection vulnerability exists in the configuration generator of NGINX Ingress Controller. Multiple user-controllable fields are written into the generated NGINX configuration without sanitization. An authenticated attacker with permission to create or modify these CRDs or annotations may craft values that inject arbitrary NGINX configuration directives. \n\nImpact:\nAn authenticated attacker granted write access to NGINX Ingress Controller CRDs or Ingress annotations through the Kubernetes API may be able to inject arbitrary NGINX configuration directives, create or delete files, or disable services. There is no data plane exposure; this is a control 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":false,"headline":"NGINX Ingress Controller vulnerability","id":"CVE-2026-55723","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Gardyn IoT Hub Exposure of Sensitive System Information to an Unauthorized Control Sphere","id":"CVE-2026-55726"},"packages":[],"prev":{"headline":"SQL Injection in StoneFly Storage Concentrator","id":"CVE-2026-55721"},"products":["NGINX Ingress Controller"],"published":"2026-07-15","related":[{"cvss_score":8.7,"headline":"NGINX Ingress Controller vulnerability","id":"CVE-2025-14727","kev_date_added":null,"published":"2025-12-17"},{"cvss_score":7.1,"headline":"NGINX Ingress Controller vulnerability","id":"CVE-2026-52865","kev_date_added":null,"published":"2026-07-15"},{"cvss_score":7,"headline":"NGINX ngx_http_hls_module vulnerability CVE-2022-41743","id":"CVE-2022-41743","kev_date_added":null,"published":"2022-10-19"},{"cvss_score":6.5,"headline":"NGINX Ingress Controller vulnerability CVE-2022-30535","id":"CVE-2022-30535","kev_date_added":null,"published":"2022-08-04"},{"cvss_score":6.5,"headline":"Security feature bypass in NGINX Ingress Controller","id":"CVE-2021-23055","kev_date_added":null,"published":"2022-04-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-16","vendors":["F5"]},"summary":"Authenticated attackers can inject arbitrary NGINX directives via unsanitized CRDs or annotations, potentially executing code or modifying files.","url":"https://insights.sbomify.com/CVE-2026-55723/"}