Service interruption via PDF-signing double free
Published May 14, 2026 · Updated May 14, 2026
Double free in PoDoFo 1.0.0 through 1.0.3 allows attackers to corrupt heap memory during PDF signing via a crafted PDF. compute_hash_to_sign frees buf after EVP_DigestUpdate, then an EVP_DigestFinal failure jumps to Error, where the nonnull pointer is freed again. The path requires user interaction and an improbable OpenSSL failure; the vendor identifies arbitrary code execution as the upper-bound consequence.
Summary
What happened
Double free in PoDoFo 1.0.0 through 1.0.3 allows attackers to corrupt heap memory during PDF signing via a crafted PDF. compute_hash_to_sign frees buf after EVP_DigestUpdate, then an EVP_DigestFinal failure jumps to Error, where the nonnull pointer is freed again. The path requires user interaction and an improbable OpenSSL failure; the vendor identifies arbitrary code execution as the upper-bound consequence.
The record
- CVE
- CVE-2026-44348
- Published
- May 14, 2026
- Updated
- May 14, 2026
- Vendor
- PoDoFo Project
- Product
- PoDoFo
- Classifications
- CWE-415, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 2026CVE publishedPublication date reported by the CVE source.
- May 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.0.0, < 1.0.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GitHub advisory proof-of-concept triggerproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo