CVE-2026-85672: zerox 1.1.20 OS Command Injection via Document URL File Extension
zerox 1.1.20 contains an OS command injection vulnerability in the file download mechanism where the temporary file extension derived from document URLs is interpolated unsanitized into shell commands executed by poppler utilities. Attackers can craft document URLs with malicious file extensions containing command substitution syntax to execute arbitrary OS commands before document processing occurs.
Security readout for executives and security teams
Plain-English summary
A malicious document URL may cause zerox 1.1.20 to run attacker-chosen operating-system commands on the processing server. A successful attack could expose data, alter systems, or interrupt service without authentication or user interaction. Risk depends on whether an application accepts attacker-controlled document URLs.
Executive priority
Prioritize immediate exposure assessment for internet-facing document-processing systems. If zerox 1.1.20 receives untrusted URLs, reduce reachability and privileges now while awaiting or confirming vendor remediation. Absence from KEV is not evidence that exploitation is impossible.
Technical view
The temporary file extension is derived from a document URL and reportedly inserted without sanitization into shell commands invoking Poppler utilities. A crafted extension containing shell command-substitution syntax can trigger arbitrary command execution before document processing. This is classified as CWE-78 with CVSS 3.1 score 9.8.
Likely exposure
Highest exposure exists where zerox 1.1.20 processes document URLs supplied by unauthenticated or untrusted users. Internet-facing upload, conversion, OCR, or document-ingestion services warrant urgent review. The bundle's affected-version metadata conflicts with its title and description, so exact version scope requires vendor confirmation.
Exploitation context
The supplied record does not identify CISA KEV listing or provide evidence of active exploitation. However, the reported network-accessible, low-complexity path requires neither privileges nor user interaction. Treat reachable deployments as high risk while distinguishing theoretical exploitability from confirmed attacks.
Researcher notes
The core claim is command injection through URL-derived extension handling before Poppler processing. The bundle names 1.1.20, but its structured affected entry lists version "0" with default status unaffected. Researchers should preserve this discrepancy, validate vulnerable tags or commits, and avoid broadening the affected range without authoritative confirmation.
Mitigation direction
Identify deployments using zerox and determine whether version 1.1.20 is present.
Temporarily reject or strictly allowlist untrusted document URLs and permitted file extensions.
Restrict the document processor's operating-system privileges and network access.
Monitor the GitHub issue and vendor repository for confirmed remediation guidance.
Apply a vendor-supported fixed release when one is explicitly identified.
Validation and detection
Inventory applications, containers, and services that depend on zerox.
Trace whether untrusted users can control document URLs or their extensions.
Review logs for unusual shell activity originating from document-processing services.
Confirm processors run with minimal filesystem, credential, and network permissions.
Verify the installed version against updated vendor and CVE guidance.
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-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter 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.
2CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-78 · source CWE mapping
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.