{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-25746 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-25746 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-25746 is a high-severity missing authorization vulnerability in Kubernetes ingress-nginx, published on 6 May 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-25746 and fix it if it is affected.\n\nWhat it is: CVE-2021-25746 is a high-severity missing authorization vulnerability in Kubernetes ingress-nginx, published on 6 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-25746 in the wild and no public exploit code.\n\nAffected product: Kubernetes ingress-nginx. 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-2021-25746/ (Markdown: https://insights.sbomify.com/CVE-2021-25746/index.md)","id":"CVE-2021-25746","markdown":"https://insights.sbomify.com/CVE-2021-25746/index.md","name":"CVE-2021-25746","record":{"aliases":["GHSA-79xv-4hmm-pw72"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes ingress-nginx","requires_auth":"low_privilege","summary":"Users with ingress creation rights can inject annotations to steal controller credentials, granting access to all cluster secrets.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"kubernetes","cpe":[{"product":"ingress-nginx","vendor":"kubernetes"}],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use .metadata.annotations in an Ingress object (in the networking.k8s.io or extensions API group) to obtain the credentials of the ingress-nginx controller. In the default configuration, that credential has access to all secrets in the cluster.","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":"Ingress-nginx directive injection via annotations","id":"CVE-2021-25746","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Ingress-nginx `path` sanitization can be bypassed with newline character","id":"CVE-2021-25748"},"packages":[],"prev":{"headline":"Ingress-nginx path can be pointed to service account token file","id":"CVE-2021-25745"},"products":["Kubernetes ingress-nginx"],"published":"2022-05-06","related":[{"cvss_score":8.8,"headline":"ingress-nginx rewrite-target nginx configuration injection","id":"CVE-2026-3288","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":8.8,"headline":"Ingress-nginx `path` sanitization can be bypassed with `log_format` directive","id":"CVE-2022-4886","kev_date_added":null,"published":"2023-10-25"},{"cvss_score":7.6,"headline":"Ingress nginx annotation injection causes arbitrary command execution","id":"CVE-2023-5043","kev_date_added":null,"published":"2023-10-25"},{"cvss_score":7.6,"headline":"Code injection via nginx.ingress.kubernetes.io/permanent-redirect annotation","id":"CVE-2023-5044","kev_date_added":null,"published":"2023-10-25"},{"cvss_score":7.6,"headline":"Ingress-nginx `path` sanitization can be bypassed with newline character","id":"CVE-2021-25748","kev_date_added":null,"published":"2023-05-24"},{"cvss_score":7.6,"headline":"Ingress-nginx path can be pointed to service account token file","id":"CVE-2021-25745","kev_date_added":null,"published":"2022-05-06"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["Kubernetes"]},"summary":"Users with ingress creation rights can inject annotations to steal controller credentials, granting access to all cluster secrets.","url":"https://insights.sbomify.com/CVE-2021-25746/"}