Skip to main content
VulnerabilityPublished Updated

CVE-2025-9394: PoDoFo · Use After Free

Affects PoDoFoSource CVE Database V5

0

Public exploit available · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
PoDoFoAffected
  • =1.1.0-dev
Fixed in–

AI-suggested

  1. Immediate application of the official patch (commit 22d16cb142f293bf956f66a4d399cdd65576d36c) to all instances of PoDoFo 1.1.0-dev in use is critical.
  2. Conduct an inventory of all software and systems using PoDoFo to identify affected versions.
  3. Where patching is not immediately feasible, implement strict access controls to limit local user privileges and prevent untrusted users from accessing systems running vulnerable PoDoFo versions.
  4. Monitor logs and system behavior for unusual crashes or anomalies in PDF processing applications that could indicate exploitation attempts.
  5. Employ application whitelisting and endpoint protection to detect and block exploitation attempts.
  6. For development teams, review and harden memory management practices in PDF parsing code to prevent similar vulnerabilities.
  7. Educate users and administrators about the risks of opening untrusted PDF files, especially on systems where PoDoFo is used.
  8. Consider sandboxing or isolating PDF processing components to limit the impact of potential exploitation.

Description

A flaw has been found in PoDoFo 1.1.0-dev. This issue affects the function PdfTokenizer::DetermineDataType of the file src/podofo/main/PdfTokenizer.cpp of the component PDF Dictionary Parser. Executing manipulation can lead to use after free. It is possible to launch the attack on the local host. The exploit has been published and may be used. This patch is called 22d16cb142f293bf956f66a4d399cdd65576d36c. A patch should be applied to remediate this issue.

References

Community reviews

Loading reviews…