LiveActive security incident?Get immediate response
CVE Record

CVE-2026-26157: Busybox: busybox: arbitrary file overwrite and potential code execution via incomplete path sanitization

A flaw was found in BusyBox. Incomplete path sanitization in its archive extraction utilities allows an attacker to craft malicious archives that when extracted, and under specific conditions, may write to files outside the intended directory. This can lead to arbitrary file overwrite, potentially enabling code execution through the modification of sensitive system files.

HighCVSS 7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

BusyBox archive extraction can be tricked into writing files outside the chosen extraction directory. If a vulnerable system extracts a malicious archive under the right conditions, important files could be overwritten, potentially leading to code execution.

Executive priority

Treat as high priority where BusyBox handles untrusted archives in images, embedded systems, or operational tooling. Business urgency is lower where archive extraction is tightly controlled, but affected Red Hat Hardened Images should be remediated through vendor updates.

Technical view

CVE-2026-26157 is incomplete path sanitization in BusyBox archive extraction utilities, mapped to CWE-73. CVSS 3.1 is 7.0 with local attack vector, high complexity, no privileges required, user interaction required, and high confidentiality, integrity, and availability impact.

Likely exposure

Confirmed affected data in the bundle names Red Hat Hardened Images with busybox-main 1.37.0-7.2.hum1. Red Hat Enterprise Linux 6 busybox is listed with unknown status. Other exposure should be verified against vendor advisories, including Siemens guidance referenced by the CVE.

Exploitation context

The bundle does not show CISA KEV listing or cited active exploitation. Exploitation requires a malicious archive to be extracted and depends on specific extraction conditions, but successful abuse could overwrite sensitive files and enable follow-on code execution.

Researcher notes

The available evidence supports arbitrary file overwrite risk through archive extraction path handling. Public bundle references an upstream BusyBox archival commit, Red Hat advisory data, Red Hat Bugzilla, and Siemens advisory, but does not provide enough detail here to claim exploit availability or exact fixed versions.

Mitigation direction

  • Apply vendor-provided updates from Red Hat advisory RHSA-2026:13831 where applicable.
  • Check Siemens and other product vendor guidance for affected embedded BusyBox use.
  • Avoid extracting untrusted archives with vulnerable BusyBox utilities.
  • Run archive extraction with least privilege in constrained, disposable directories.
  • Monitor sensitive system files for unexpected changes after archive handling.

Validation and detection

  • Inventory BusyBox versions and package names across images, appliances, and containers.
  • Check for Red Hat Hardened Images using busybox-main 1.37.0-7.2.hum1.
  • Confirm RHEL 6 busybox status with Red Hat because the bundle marks it unknown.
  • Identify workflows that extract attacker-supplied or external archives.
  • Verify patched package status against vendor advisory records.
Prepared
Confidence
medium
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-73: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-26157 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
7Timeline events
3ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7CVSS 3.1HighCVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H15.9redhat
7CVSS 3.1HighCVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H15.9redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7High
CVSS 3.1 vector shape for CVE-2026-26157Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. ADP timelineredhat-SADP

    Made public.

  2. Source timelineredhat

    Made public.

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. Source timelineredhat

    Reported to Red Hat.

  6. CVE publishedCVE Program

    The CVE record was published.

  7. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
siemens-SADPADP container
redhat-SADPbusybox: BusyBox: Arbitrary file overwrite and potential code execution via incomplete path sanitization
other:Red Hat severity ratingcvssV3_1
  • 2026-02-11T17:54:52.728Z: Reported to Red Hat.
  • 2026-02-11T00:00:00.000Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Red HatRed Hat Hardened Imagesbusybox-main, 1.37.0-7.2.hum1affected
Red HatRed Hat Enterprise Linux 6busyboxunknown
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-73 · source CWE mapping

External Control of File Name or Path

External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.