{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-2270 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-2270 is a medium-severity vulnerability in Kubernetes, published on 26 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-2270 and fix it if it is affected.\n\nWhat it is: CVE-2026-2270 is a medium-severity vulnerability in Kubernetes, published on 26 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-2270 in the wild and no public exploit code.\n\nAffected product: Kubernetes. 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-2270/ (Markdown: https://insights.sbomify.com/CVE-2026-2270/index.md)","id":"CVE-2026-2270","markdown":"https://insights.sbomify.com/CVE-2026-2270/index.md","name":"CVE-2026-2270","record":{"aliases":["AZL-111140","DEBIAN-CVE-2026-2270","GHSA-3jhc-p65m-8464"],"analysis":null,"analysis_generated_by":null,"assigner":"kubernetes","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"A confused deputy attack exists in the StatefulSet controller that allows a user with namespace-scoped write permissions on StatefulSet and ControllerRevision objects to create a cross-namespace pod. An attacker exploiting this vulnerability would have full control over the resulting pod’s metadata and specification, including namespace selection. Note that the cross-namespace pod will be immediately deleted by the garbage collector unless the attacker is able to construct a valid StatefulSet OwnerReference. This would require referencing the UID of an existing StatefulSet in the victim’s namespace.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"StatefulSet and ControllerRevision write permissions allow cross-namespace pod creation","id":"CVE-2026-2270","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Gimp: gimp: denial of service via crafted psp image file","id":"CVE-2026-2271"},"packages":[],"prev":{"headline":"Server-side request forgery in Uncanny Automator – Easy Automation, Integration, Webhooks \u0026 Workflow Builder Plugin","id":"CVE-2026-2269"},"products":["Kubernetes"],"published":"2026-10-26","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-29","vendors":["Kubernetes"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-2270/"}