Skip to main content
CVE-2026-114609VulnerabilityPublished Updated

Ocrmypdf: fpdf2 implicitly loads external URLs and local image paths when rendering attacker-controlled content

Affects ocrmypdfSource GCVE Database

0
Compare
Authoritative record:CVE-2026-114609· Medium 5.8

Not known to be exploited · CVSS 5.8 Medium : upgrade to 17.11.0 when convenient.

Data as of 10 Nov 2026, 18:55 UTC

CVSS 3.1 base score
5.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.8
Patch
Available – fixed in 17.11.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade ocrmypdf to 17.11.0.

Affected software

ProductAffectedFixed in
Homebrewocrmypdfpkg:brew/ocrmypdfOther threatsAffected
  • >=17.0.0 <17.11.0
Fixed in
  • 17.11.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in ocrmypdf version 17.11.0 that fixes this issue. Users should upgrade to this version or later. Until patched, applications should avoid rendering untrusted HTML, SVG, or template content with fpdf2 APIs that load images. Additional mitigations include rejecting or sanitizing user-controlled image source values, implementing allowlists for resource loading, or converting user-supplied images to trusted in-memory objects before passing them to fpdf2. No vendor advisory states that no action is required.

Description

The vulnerability in ocrmypdf arises from the fpdf2 library's behavior of implicitly loading external URLs and local image paths when rendering attacker-controlled content. This can lead to outbound HTTP(S) requests or local file access attempts if untrusted HTML, SVG, or image paths are rendered without proper sanitization. The issue affects versions from 17.0.0 up to but not including 17.11.0. The severity is medium with a CVSS score of 5.8. A fix is available in version 17.11.0.

References

Community reviews

Loading reviews…