{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33243 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-33243 is a high-severity vulnerability in barebox, published on 20 Mar 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-33243 and fix it if it is affected.\n\nWhat it is: CVE-2026-33243 is a high-severity vulnerability in barebox, published on 20 Mar 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-33243 in the wild and no public exploit code.\n\nAffected product: barebox. 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-33243/ (Markdown: https://insights.sbomify.com/CVE-2026-33243/index.md)","id":"CVE-2026-33243","markdown":"https://insights.sbomify.com/CVE-2026-33243/index.md","name":"CVE-2026-33243","record":{"aliases":["OESA-2026-1834"],"analysis":{"component_type":"hardware_firmware","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"barebox bootloader","requires_auth":"high_privilege","summary":"An attacker can bypass FIT signature verification in barebox to boot unverified images by modifying the hashed-nodes property.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"barebox","vendor":"pengutronix"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"barebox is a bootloader. In barebox from version 2016.03.0 to before version 2026.03.1 (and the corresponding backport to 2025.09.3), an attacker could exploit a FIT signature verification vulnerability to trick the bootloader into booting different images than those that were verified as part of a signed configuration. mkimage(1) sets the hashed-nodes property of the FIT signature node to list which nodes of the FIT were hashed as part of the signing process as these will need to be verified later on by the bootloader. However, hashed-nodes itself is not part of the hash and could therefore be modified to allow booting different images than those that have been verified. This issue has been patched in barebox versions 2026.03.1 and backported to 2025.09.3.","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":"barebox: FIT Signature Verification Bypass Vulnerability","id":"CVE-2026-33243","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"React Router has stored XSS via unescaped Location header in prerendered redirect HTML","id":"CVE-2026-33244"},"packages":[],"prev":{"headline":"Salvo has a Path Traversal in salvo-proxy::encode_url_path allows API Gateway Bypass","id":"CVE-2026-33242"},"products":["barebox"],"published":"2026-03-20","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-15937","kev_date_added":null,"published":"2019-09-05"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-15938","kev_date_added":null,"published":"2019-09-05"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2020-13910","kev_date_added":null,"published":"2020-06-07"},{"cvss_score":8.6,"headline":"barebox EFI PE Loader Memory Safety Vulnerabilities","id":"CVE-2026-34963","kev_date_added":null,"published":"2026-05-11"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2021-37847","kev_date_added":null,"published":"2021-08-02"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2021-37848","kev_date_added":null,"published":"2021-08-02"}],"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-03-26","vendors":["barebox"]},"summary":"An attacker can bypass FIT signature verification in barebox to boot unverified images by modifying the hashed-nodes property.","url":"https://insights.sbomify.com/CVE-2026-33243/"}