Skip to main content
VulnerabilityPublished Updated

CVE-2023-38745: pandoc

Affects pandocSource CVE Database V5

0

Mentioned vulnerabilities

Not known to be exploited : upgrade to 3.1.6 soon.

Data as of 26 Oct 2026, 13:47 UTC

Severity
High

Rated High by the CNA (mitre) · No CVSS score from NVD or the CNA

EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.1.6

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade jgm/pandoc to 3.1.6.

Affected software

ProductAffectedFixed in
GitHubjgm/pandocpkg:github/jgm/pandocOther threatsAffected
  • <3.1.6
Fixed in
  • 3.1.6

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

AI-suggested

A fix is available in Pandoc version 3.1.6. Users should upgrade to version 3.1.6 or later to remediate this vulnerability. Until upgraded, avoid processing untrusted input with the --extract-media option or generating PDF output using vulnerable versions of Pandoc.

Description

Pandoc versions prior to 3.1.6 contain a vulnerability that allows arbitrary file write. This occurs when processing crafted image elements in input while generating files using the --extract-media option or when outputting to PDF format. The flaw stems from an incomplete fix for a previous vulnerability (CVE-2023-35936) related to double encoded path names. Exploitation requires passing untrusted input to Pandoc with these specific options enabled, and the impact depends on the privileges of the Pandoc process.

References

Community reviews

Loading reviews…