Security readout for executives and security teams
Plain-English summary
PyMuPDF 1.26.5 is reported to allow path traversal leading to arbitrary file writes. In business terms, a vulnerable workflow could let a lower-privileged local actor influence where files are written after user interaction, potentially affecting sensitive data, integrity, and system availability.
Executive priority
High priority for teams using PyMuPDF 1.26.5 in business workflows. The strongest action is rapid inventory, exposure scoping, and vendor-guided remediation, rather than emergency assumptions about active exploitation.
Technical view
The source bundle describes CWE-22 path traversal and arbitrary file write in the embedded get function in _main_.py for PyMuPDF 1.26.5. CVSS 3.1 is 8.2 with local attack vector, low complexity, low privileges required, user interaction required, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to environments that package or run PyMuPDF version 1.26.5, especially where local users or workflows can trigger PyMuPDF processing. The provided sources do not establish broader product impact beyond PyMuPDF 1.26.5.
Exploitation context
The bundle does not cite CISA KEV listing or public active exploitation. Treat this as high risk because arbitrary file write can be serious, but do not assume exploitation in the wild from the provided evidence.
Researcher notes
Evidence is concise and does not include exploit details, fixed versions, or confirmed real-world exploitation. The CVSS vector indicates local execution conditions with required interaction and high impact. Validate affected status against actual dependency use and vendor advisories.
Mitigation direction
Inventory systems and applications for PyMuPDF version 1.26.5.
Check Artifex, CERT/CC, and Red Hat guidance for fixed versions or vendor mitigations.
Prioritize remediation on systems handling untrusted or user-influenced documents.
Restrict vulnerable workflows to trusted users until vendor guidance is applied.
Update dependency locks, container images, and SBOM records after remediation.
Validation and detection
Confirm installed PyMuPDF versions in package manifests, SBOMs, and runtime images.
Identify applications or jobs that invoke PyMuPDF in user-influenced workflows.
Review CERT/CC and Red Hat records for updated affected-status or fix information.
Verify remediation by confirming PyMuPDF 1.26.5 is absent where exposure exists.
Document exceptions where vendor guidance says a product is not affected.
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-22: 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.
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.
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
5Timeline events
3ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: 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-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.