Security readout for executives and security teams
Plain-English summary
A crafted tar archive can conceal attacker-controlled files from checks performed before extraction. If a user or automated process then extracts the archive, hidden malicious content may be written to the system. The main consequence is compromised file integrity, not disclosed data theft or service outage.
Executive priority
Prioritize affected systems that automatically extract externally supplied archives or write into sensitive locations. This is not presented as an emergency internet-wide compromise, but the potential for attacker-controlled file placement warrants timely inventory, containment, and vendor-guided remediation. Lower-risk systems can follow normal patch governance after exposure is confirmed.
Technical view
CVE-2026-5704 is a CWE-434 hidden-file injection flaw in tar. Its CVSS 3.1 score is 5.0: local execution path, low complexity, low privileges, required user interaction, and high integrity impact. The supplied record says crafted archives can bypass pre-extraction inspection, but does not describe the underlying parsing defect.
Likely exposure
The supplied data marks tar on Red Hat Enterprise Linux 6, 7, 8, 9, and 10, plus Red Hat Hardened Images, as affected. Exposure is greatest where users, CI/CD jobs, upload services, or other automation inspect and extract untrusted archives. Exact vulnerable package versions are not provided.
Exploitation context
An attacker can deliver a malicious archive remotely, but successful exploitation requires local extraction and user interaction according to the CVSS vector. The provided sources do not establish active exploitation, public weaponization, or CISA KEV listing. The key security boundary is trusting pre-extraction inspection to reveal every resulting file.
Researcher notes
The record supports hidden-file injection and high integrity impact, but omits affected package versions, root-cause detail, fixed releases, patches, and exploitation telemetry. Researchers should distinguish remote delivery from the local, user-assisted execution path represented by the CVSS vector. Claims about specific hidden-file mechanisms or post-extraction execution would exceed the supplied evidence.
Mitigation direction
- Check Red Hat guidance and applicable errata for each installed tar package; no specific fixed version is supplied.
- Avoid extracting untrusted archives on production systems until vendor remediation status is confirmed.
- Isolate necessary archive extraction in a restricted environment with minimal filesystem permissions.
- Do not treat pre-extraction file listings or inspection alone as proof that an archive is safe.
- Monitor extraction destinations for newly created hidden files and unexpected integrity changes.
Validation and detection
- Inventory tar packages across the listed Red Hat platforms and map them to current vendor advisories.
- Identify services, pipelines, and user workflows that accept or automatically extract externally supplied archives.
- Confirm whether archive controls inspect only before extraction or also validate the resulting filesystem contents.
- Review extraction directories for unexpected hidden files, prioritizing privileged and automated workflows.
- After remediation, verify vendor-designated package versions are installed and archive handling controls remain effective.
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-434: 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 lookupCVE-2026-5704 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
- Medium
- CVSS
- 5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N
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
1 official scoreWe 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:L/PR:L/UI:R/S:U/C:N/I:H/A:N1.33.6redhatVulnerability scoring details
Base CVSS 3.1 score
5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Reported to Red Hat.
- Source timelineredhat
Made public.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- 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
Source materials
- CVE List V5 sourceCVE List V5
- https://access.redhat.com/security/cve/CVE-2026-5704CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2455360CVE reference, redhat · issue-tracking, x_refsource_REDHAT
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.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.