{"answers":{"affected":"1 open source package ship an affected version, including kyverno.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100704 exists.","fix":"Upgrade kyverno to 1.19.1 or later.","what":"CVE-2026-100704 is a high-severity vulnerability in kyverno, published on 26 Sep 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-100704 and fix it if it is affected.\n\nWhat it is: CVE-2026-100704 is a high-severity vulnerability in kyverno, published on 26 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100704 exists.\n\nAffected packages and fixed versions:\n- kyverno (Bitnami): affected from 1.14.0; fixed in 1.19.1\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-100704/ (Markdown: https://insights.sbomify.com/CVE-2026-100704/index.md)","id":"CVE-2026-100704","markdown":"https://insights.sbomify.com/CVE-2026-100704/index.md","name":"CVE-2026-100704","record":{"aliases":["BIT-kyverno-2026-100704","GHSA-435c-9ffq-3prr","GHSA-5cjf-wwfg-pj4c","MINI-29jx-c3v6-3m72","MINI-2w89-g84p-q7rf","MINI-72mh-m64m-jqx7","MINI-85rr-2h5r-8p5p","MINI-96wm-8hh6-g95r","MINI-9rxm-v5p6-6p78","MINI-cv3x-wx8v-w8hw","MINI-fr9c-c849-wvg9","MINI-mpj4-234q-j3rx","MINI-w4wg-qx9j-3qh6"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes policy engine","requires_auth":"low_privilege","summary":"Attackers can bypass image signature verification in Kyverno by exploiting a flaw in PolicyException handling, allowing unsigned images into the cluster.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Kyverno is a policy engine for Kubernetes. In versions 1.14.0 through 1.19.0, the ImageValidatingPolicy (policies.kyverno.io/v1beta1) evaluator never reads the spec.images and spec.allowedValues fields of a PolicyException. Any PolicyException whose policyRefs and matchConditions match a resource causes image signature verification to be skipped for the entire resource rather than only for the listed images or values, so an exception intended to exempt a single trusted image exempts every image on the matched resource(s). As a result, unsigned or untrusted images can be admitted to the cluster without signature verification. This differs from ValidatingPolicy, GeneratingPolicy, and MutatingPolicy, which treat the same field as a partial exemption. The issue is fixed in version 1.19.1.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Kyverno before 1.19.1 ImageValidatingPolicy Exception Bypass","id":"CVE-2026-100704","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":1,"n_references":2,"next":{"headline":"Kyverno before 1.19.1 SSRF via legacy apiCall service executor","id":"CVE-2026-100705"},"packages":[{"ecosystem":"Bitnami","fixed":["1.19.1"],"introduced":["1.14.0"],"last_affected":[],"package":"kyverno","purl":"pkg:bitnami/kyverno","source":"BIT-kyverno-2026-100704"}],"prev":{"headline":"Kyverno before 1.19.1 Cross-Namespace Data Access via globalcontext.Lib","id":"CVE-2026-100703"},"products":["kyverno"],"published":"2026-09-26","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-28","vendors":["kyverno"]},"summary":"Attackers can bypass image signature verification in Kyverno by exploiting a flaw in PolicyException handling, allowing unsigned images into the cluster.","url":"https://insights.sbomify.com/CVE-2026-100704/"}