CVE-2026-33243 | barebox up to 2025.09.2/2026.03.0 data authenticity (GHSA-3fvj-q26p-j6h4)

VDB-352303 · CVE-2026-33243 · GHSA-3FVJ-Q26P-J6H4 BAREBOX UP TO 2025.09.2/2026.03.0 DATA AUTHENTICITY HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 7.3 $0-$5k 0.81+ Summaryinfo A vulnerability was found in barebox up to 2025.09.2/2026.03.0. It has been rated as critical. The affected element is an unknown function. This manipulation causes data authenticity. This vulnerability appears as CVE-2026-33243. The attack requires local access. There is no available exploit. Upgrading the affected component is advised. Detailsinfo A vulnerability was found in barebox up to 2025.09.2/2026.03.0. It has been declared as critical. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a data authenticity vulnerability. The CWE definition for the vulnerability is CWE-345. The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is: barebox is a bootloader. In barebox from version 2016.03.0 to before version 2025.09.3 and from version 2025.10.0 to before version 2026.03.1, when creating a FIT, 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 can therefore be modified by an attacker to trick the bootloader into booting different images than those that have been verified. This issue has been patched in barebox versions 2025.09.3 and 2026.03.1. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-33243 since 03/18/2026. The exploitation appears to be easy. Attacking locally is a requirement. Additional levels of successful authentication are necessary for exploitation. The technical details are unknown and an exploit is not publicly available. Upgrading to version 2025.09.3 or 2026.03.1 eliminates this vulnerability. Applying the patch aca01795056d51060cb096f9a1ea309361743e05 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Name barebox Version 2025.09.0 2025.09.1 2025.09.2 2026.03 License open-source Website Product: https://github.com/barebox/barebox/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 7.4 VulDB Meta Temp Score: 7.3 VulDB Base Score: 6.7 VulDB Temp Score: 6.4 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 8.2 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Data authenticity CWE: CWE-345 CAPEC: 🔒 ATT&CK: 🔒 Physical: Partially Local: Yes Remote: No Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: barebox 2025.09.3/2026.03.1 Patch: aca01795056d51060cb096f9a1ea309361743e05 Timelineinfo 03/18/2026 CVE reserved 03/21/2026 +3 days Advisory disclosed 03/21/2026 +0 days VulDB entry created 03/21/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-3fvj-q26p-j6h4 Status: Confirmed CVE: CVE-2026-33243 (🔒) GCVE (CVE): GCVE-0-2026-33243 GCVE (VulDB): GCVE-100-352303 Entryinfo Created: 03/21/2026 08:13 Changes: 03/21/2026 08:13 (64) Complete: 🔍 Cache ID: 99:66E:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸