Skip to main content

Barebox CVE-2026-33243

HIGH
Insufficient Verification of Data Authenticity (CWE-345)
2026-03-20 GitHub_M
8.2
CVSS 3.1 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Modify hashed-nodes property in FIT signature
  2. Exploit
    Bootloader verifies wrong image nodes
  3. Execution
    Load unverified malicious kernel or rootfs
  4. Impact
    Execute arbitrary code with bootloader privileges

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V15 - Secure Coding and Architecture Data authenticity verification
Exploitation Conditions

Attacker with high-privilege local access to the barebox build system must modify the FIT (Flattened Image Tree) image file after signing but before deployment. Affects barebox versions 2016.03.0–2025.09.2 and 2025.10.0–2026.03.0. The hashed-nodes property in the FIT signature node can be altered to trick bootloader verification of different images.

Impact

The CVSS score of 8.2 (High) reflects significant impact with Changed scope, but real-world risk is constrained by the PR:H (High Privileges Required) and AV:L (Local Access) requirements. An attacker needs existing privileged access to the boot environment to modify FIT images before verification occurs. No EPSS score or KEV listing is provided in the intelligence, and no public proof-of-concept is explicitly mentioned, though a patch commit is publicly available at GitHub. The primary risk scenario involves supply chain attacks where an attacker with access to the image signing pipeline could create malicious images that bypass verification, or privilege escalation scenarios where a local attacker with existing root access seeks persistence through bootloader manipulation. While technically severe for secure boot bypass, the high privilege requirement significantly limits the attack surface compared to remotely exploitable vulnerabilities.

Exploit ScenarioDerived

An attacker who has compromised a firmware build system or gained privileged access to embedded device storage could create a malicious FIT image containing unauthorized kernel or initramfs components. By modifying the hashed-nodes property to exclude the malicious components from verification while keeping legitimate signatures intact, the attacker tricks the barebox bootloader into loading the malicious payload as if it were properly signed. This enables persistent compromise surviving reboots and provides a foundation for secure boot bypass in industrial IoT devices, network appliances, or embedded systems using barebox.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 20, 2026

A signature bypass vulnerability exists in the barebox bootloader's FIT (Flattened Image Tree) image verification mechanism. The hashed-nodes property, which lists which FIT nodes were signed, is not itself part of the cryptographic hash, allowing an attacker with high privileges and local access to modify this property and trick the bootloader into loading malicious images that were never signed. This affects barebox versions 2016.03.0 through 2025.09.2 and 2025.10.0 through 2026.03.0, with patches available in versions 2025.09.3 and 2026.03.1.

RemediationAI

Upgrade barebox to version 2025.09.3 or later for the 2025.09.x branch, or to version 2026.03.1 or later for the 2026.03.x branch. The fix is documented in commit aca01795056d51060cb096f9a1ea309361743e05 available at https://github.com/barebox/barebox/commit/aca01795056d51060cb096f9a1ea309361743e05. Organizations should review their bootloader versions and update according to the guidance in https://github.com/barebox/barebox/security/advisories/GHSA-3fvj-q26p-j6h4. As a defense-in-depth measure, implement strict access controls to boot media and image signing infrastructure, and establish monitoring for unauthorized modifications to FIT images in the boot chain. Where immediate patching is not feasible, consider implementing hardware-based secure boot mechanisms or verified boot chains that provide independent cryptographic validation.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Barebox is an embedded systems bootloader commonly used in industrial and embedded Linux environments. The vulnerability affects the FIT (Flattened Image Tree) image format verification process, specifically in how mkimage generates signature nodes. According to CPE cpe:2.3:a:barebox:barebox, the issue stems from CWE-345 (Insufficient Verification of Data Authenticity), where the hashed-nodes property acts as metadata describing what was signed but is not itself cryptographically protected. This architectural flaw allows the integrity check to be subverted by modifying which nodes the bootloader believes should be verified, effectively creating a semantic gap between what was signed and what gets verified during secure boot.

Know when Barebox gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 8.2 HIGH
AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Primary rating from Vendor (GitHub_M) · only source for this CVE.

CVSS VectorVendor: GitHub_M

Attack Vector
Local
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

A critical vulnerability in the barebox bootloader allows attackers with local, high-privileged access to bypass image signature verification and load malicious firmware, potentially compromising system integrity and control. Organizations using affected barebox versions face risk of unauthorized firmware modification with no available patch, requiring immediate compensating controls and inventory assessment.

Business Impact: High
Compensating Controls

Restrict local administrative and bootloader access through role-based access controls and hardware security modules; disable FIT image support if functionality permits; implement hardware-based secure boot and attestation mechanisms; enforce strict change management and audit logging for bootloader modifications; consider network-level monitoring for anomalous firmware behavior; isolate affected systems from production networks pending patch availability.

Threat Intelligence Overview

EPSS Score
0.0%
Top 100% exploitable
Data Quality
6 sources
Confidence: High
NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

41
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +41
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Affected Products (CPE)CVE.org

cpe:2.3:a:barebox:barebox:*:*:*:*:*:*:*:*

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy