Security readout for executives and security teams
Plain-English summary
BusyBox archive extraction can be tricked into writing files outside the intended folder when a user or process extracts a malicious archive. In affected images, this could overwrite sensitive files and may lead to code execution. The attack needs local extraction and user interaction, so urgency depends on whether untrusted archives are handled.
Executive priority
Treat this as high priority where BusyBox processes untrusted archives or appears in production base images. It is not currently known to be actively exploited from the provided evidence, but arbitrary file overwrite in widely reused components can become operationally serious quickly.
Technical view
The flaw is incomplete path sanitization in BusyBox archive extraction utilities, mapped to CWE-73. The CVSS 3.1 score is 7.0 with local attack vector, high complexity, no privileges required, and user interaction required. Red Hat lists Red Hat Hardened Images busybox-main 1.37.0-7.2.hum1 as affected; RHEL 6 status is unknown.
Likely exposure
Highest exposure is in container images, embedded systems, appliances, or automation that use BusyBox to unpack archives from untrusted or semi-trusted sources. Red Hat specifically identifies affected Hardened Images. Siemens has an advisory, but the prompt bundle does not identify specific Siemens products or fixed versions.
Exploitation context
The source bundle does not support active exploitation: KEV is false and no cited source states exploitation in the wild. Exploitation requires a crafted archive being extracted under specific conditions, making phishing, supply-chain package handling, CI jobs, and appliance update workflows plausible risk contexts.
Researcher notes
Focus validation on path traversal controls in BusyBox archival extraction and on real extraction call paths. Evidence is incomplete for RHEL 6 and Siemens product scope in the provided bundle. Do not assume broader BusyBox version impact beyond the cited vendor and upstream references.
Mitigation direction
- Apply Red Hat updates from RHSA-2026:13831 where applicable.
- Check BusyBox vendor guidance and the upstream archival commit for fixed versions.
- Avoid extracting untrusted archives with vulnerable BusyBox utilities.
- Run extraction in isolated directories with constrained permissions.
- Review Siemens SSA-253495 if Siemens products are in scope.
Validation and detection
- Inventory BusyBox versions in images, appliances, and base containers.
- Check for Red Hat Hardened Images using busybox-main 1.37.0-7.2.hum1.
- Confirm whether archive extraction uses BusyBox utilities in exposed workflows.
- Review CI, update, and import jobs that unpack user-supplied archives.
- Track vendor status for products marked unknown or not detailed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupExecution 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 lookupFile 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 lookupCVE-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- 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
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H15.9redhatCVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H15.9redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
7HighVector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
7HighVector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- ADP timelineredhat-SADP
Made public.
- Source timelineredhat
Made public.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Reported to Red Hat.
- Source timelineredhat
Reported to Red Hat.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-02-11T17:54:52.728Z: Reported to Red Hat.
- 2026-02-11T00:00:00.000Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2026:13831CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-26157CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2439039CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://git.busybox.net/busybox/commit/archival?id=3fb6b31c716669e12f75a2accd31bb7685b1a1cbCVE reference, redhat
- https://cert-portal.siemens.com/productcert/html/ssa-253495.htmlCVE reference, siemens-SADP
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-26157.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.