{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-11836 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-11836 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-11836 is a low-severity vulnerability in Caliptra Core Firmware, published on 4 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-11836 and fix it if it is affected.\n\nWhat it is: CVE-2026-11836 is a low-severity vulnerability in Caliptra Core Firmware, published on 4 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-11836 in the wild and no public exploit code.\n\nAffected product: Caliptra Core Firmware. 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-11836/ (Markdown: https://insights.sbomify.com/CVE-2026-11836/index.md)","id":"CVE-2026-11836","markdown":"https://insights.sbomify.com/CVE-2026-11836/index.md","name":"CVE-2026-11836","record":{"aliases":["GHSA-hw68-jjx4-m376"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Caliptra Core Firmware","requires_auth":"high_privilege","summary":"An attacker with access to the signing service can unlock debug on unintended devices sharing a key hash, bypassing per-device scope enforcement.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Caliptra","cpe":[],"cvss":{"score":1.8,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Insufficient verification of data authenticity in Caliptra Core ROM and Core Firmware (validate_debug_unlock_token()) in subsystem mode allows an attacker with access to the integrator's debug unlock signing service to unlock production debug on an unintended device by presenting a valid token issued for a different device sharing the same debug unlock key hash. The 384-bit challenge nonce continues to prevent replay of previously issued tokens. Practical impact is limited to loss of per-device scope enforcement within a set of devices that share the same unlock authority by design; it does not enable debug unlock on devices outside that set.\n\nThis issue affects Core ROM: 2.0.0 through 2.0.2, 2.1.0 through 2.1.1; Core Firmware: 2.0.0 through 2.0.1, 2.1.0.","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":"Production Debug-Unlock Token Verification Missing Device Binding","id":"CVE-2026-11836","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Ansible-collection-ansible-posix: ansible.posix authorized_key: local privilege escalation via symlink-following chown","id":"CVE-2026-11837"},"packages":[],"prev":{"headline":"Caliptra Update-Reset Secure-Boot Bypass via Attacker-Chosen AXI Staging Address (TOCTOU)","id":"CVE-2026-11835"},"products":["Core Firmware","Core ROM"],"published":"2026-08-04","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":"partial"},"state":"PUBLISHED","updated":"2026-08-04","vendors":["Caliptra"]},"summary":"An attacker with access to the signing service can unlock debug on unintended devices sharing a key hash, bypassing per-device scope enforcement.","url":"https://insights.sbomify.com/CVE-2026-11836/"}