CVE-2026-48962: IO::Compress versions before 2.220 for Perl can execute arbitrary code in File::GlobMapper via an attacker-controlled output glob
IO::Compress versions before 2.220 for Perl can execute arbitrary code in File::GlobMapper via an attacker-controlled output glob.
_parseOutputGlob() wraps the caller-supplied output glob string in double quotes and stores it in the parser state; _getFiles() then runs the stored expression through eval STRING. A literal double quote in the output glob closes the dquote wrapper, and the characters that follow are evaluated as Perl.
Arbitrary Perl in the output glob executes at the calling process's privilege.
Security readout for executives and security teams
Plain-English summary
A flaw in Perl's IO::Compress before version 2.220 can let malicious output-glob input run code with the affected process's privileges. Impact may include data theft, modification, or service disruption. Risk depends on whether an application passes attacker-controlled output globs into File::GlobMapper.
Executive priority
Prioritize prompt remediation where untrusted users can influence file-mapping or archive workflows, especially privileged services. Systems merely containing the package without a reachable attacker-controlled output-glob path have lower immediate exposure, but should remain in the upgrade program. No active exploitation is established by the supplied evidence.
Technical view
File::GlobMapper stores a caller-supplied output glob inside double quotes, then evaluates it using Perl eval STRING. An embedded double quote can escape that wrapper, causing subsequent input to be interpreted as Perl code. The issue is classified as CWE-94/CWE-95 and scored CVSS 3.1 7.8.
Likely exposure
Exposure requires IO::Compress earlier than 2.220 and a reachable workflow that supplies attacker-controlled output-glob content to File::GlobMapper. The CVSS vector describes local access with low privileges, no user interaction, and potential high confidentiality, integrity, and availability impact. The supplied package metadata is insufficient for identifying every affected distribution package.
Exploitation context
The source bundle does not report known active exploitation, and the CVE is not marked as present in KEV. Exploitation still requires control over the relevant output-glob input. Successful abuse executes Perl within the calling process's security context; network reachability depends on how an application exposes that input.
Researcher notes
The vulnerable pattern combines quote-based expression construction with eval STRING. Review should focus on data flow into the output-glob parameter and the effective privileges of the caller. The upstream patch and 2.220 release notes are the strongest supplied remediation references. Do not infer remote exposure without application-specific evidence.
Mitigation direction
Upgrade IO::Compress to version 2.220 or later.
Apply applicable Red Hat security updates on vendor-managed systems.
Prevent untrusted input from controlling File::GlobMapper output globs.
Check vendor guidance before applying distribution-specific package changes.
Validation and detection
Inventory installed and bundled IO::Compress versions, including application-local Perl dependencies.
Identify every File::GlobMapper call and trace the source of its output-glob argument.
Confirm production workloads resolve to IO::Compress 2.220 or a vendor-patched package.
Test that untrusted users cannot influence output-glob values after remediation.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process 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.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process 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.
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.
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.
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.