CVE-2023-35936

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Pandoc is a Haskell library for converting from one markup format to another, and a command-line tool that uses this library. Starting in version 1.13 and prior to version 3.1.4, Pandoc is susceptible to an arbitrary file write vulnerability, which can be triggered by providing a specially crafted image element in the input when generating files using the --extract-media option or outputting to PDF format. This vulnerability allows an attacker to create or overwrite arbitrary files on the system ,depending on the privileges of the process running pandoc. It only affects systems that pass untrusted user input to pandoc and allow pandoc to be used to produce a PDF or with the --extract-media option.

The fix is to unescape the percent-encoding prior to checking that the resource is not above the working directory, and prior to extracting the extension. Some code for checking that the path is below the working directory was flawed in a similar way and has also been fixed. Note that the --sandbox option, which only affects IO done by readers and writers themselves, does not block this vulnerability. The vulnerability is patched in pandoc 3.1.4. As a workaround, audit the pandoc command and disallow PDF output and the --extract-media option.

CVSS v3
6.1
EG Score
6.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity61% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

July 5, 2023

Last Modified

February 13, 2025

Affected Packages

(7 across 5 ecosystems)
Debian:13(2)
PackageVulnerable rangeFixed inDependents
haskell-pandoc3.0.1-2
pandoc2.17.1.1-2
Debian:14(2)
PackageVulnerable rangeFixed inDependents
haskell-pandoc3.0.1-2
pandoc2.17.1.1-2
Debian:10(1)
PackageVulnerable rangeFixed inDependents
pandoc2.2.1-32.2.1-3+deb10u1
Debian:11(1)
PackageVulnerable rangeFixed inDependents
pandoc2.9.2.1-12.9.2.1-1+deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
pandoc2.17.1.1-1.12.17.1.1-2~deb12u1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 162 total refreshes for this CVE.

  1. 2026-09-07 15:59 UTCEPSS rescore
  2. 2026-09-06 13:45 UTCEPSS rescore
  3. 2026-09-05 15:26 UTCEPSS rescore
  4. 2026-09-04 13:58 UTCEPSS rescore
  5. 2026-09-04 05:04 UTCEPSS rescore
  6. 2026-09-04 01:59 UTCOSV refresh
  7. 2026-09-02 14:09 UTCEPSS rescore
  8. 2026-09-01 13:51 UTCEPSS rescore
  9. 2026-08-30 19:15 UTCEPSS rescore
  10. 2026-08-30 01:20 UTCEPSS rescore
  11. 2026-08-28 21:38 UTCEPSS rescore
  12. 2026-08-27 14:23 UTCEPSS rescore
  13. 2026-08-26 14:43 UTCEPSS rescore
  14. 2026-08-25 13:46 UTCEPSS rescore
  15. 2026-08-24 14:14 UTCEPSS rescore
  16. 2026-08-23 00:17 UTCEPSS rescore
  17. 2026-08-21 23:47 UTCEPSS rescore
  18. 2026-08-20 22:53 UTCEPSS rescore
  19. 2026-08-19 17:02 UTCEPSS rescore
  20. 2026-08-18 13:46 UTCEPSS rescore
  21. 2026-08-17 14:06 UTCOSV refresh
  22. 2026-08-17 13:45 UTCEPSS rescore
  23. 2026-08-16 14:54 UTCEPSS rescore
  24. 2026-08-16 02:12 UTCEPSS rescore
  25. 2026-08-15 01:28 UTCEPSS rescore
Show 75 more
  1. 2026-08-13 21:58 UTCEPSS rescore
  2. 2026-08-12 13:48 UTCEPSS rescore
  3. 2026-08-11 13:39 UTCEPSS rescore
  4. 2026-08-09 13:44 UTCEPSS rescore
  5. 2026-08-08 16:34 UTCEPSS rescore
  6. 2026-08-07 16:24 UTCEPSS rescore
  7. 2026-08-06 13:44 UTCEPSS rescore
  8. 2026-08-05 19:15 UTCEPSS rescore
  9. 2026-08-05 19:15 UTCEPSS rescore
  10. 2026-08-04 15:07 UTCEPSS rescore
  11. 2026-08-04 10:35 UTCEPSS rescore
  12. 2026-08-03 10:34 UTCEPSS rescore
  13. 2026-08-02 08:45 UTCOSV refresh
  14. 2026-08-02 02:25 UTCEPSS rescore
  15. 2026-08-01 04:13 UTCEPSS rescore
  16. 2026-07-30 16:26 UTCEPSS rescore
  17. 2026-07-30 16:26 UTCEPSS rescore
  18. 2026-07-30 01:28 UTCEPSS rescore
  19. 2026-07-30 01:28 UTCEPSS rescore
  20. 2026-07-28 15:34 UTCEPSS rescore
  21. 2026-07-27 14:10 UTCEPSS rescore
  22. 2026-07-26 14:52 UTCEPSS rescore
  23. 2026-07-25 14:16 UTCEPSS rescore
  24. 2026-07-24 14:16 UTCEPSS rescore
  25. 2026-07-23 14:16 UTCEPSS rescore
  26. 2026-07-23 14:16 UTCEPSS rescore
  27. 2026-07-23 02:24 UTCEG score recompute
  28. 2026-07-22 23:11 UTCEG score recompute
  29. 2026-07-22 14:06 UTCEPSS rescore
  30. 2026-07-21 15:23 UTCEPSS rescore
  31. 2026-07-21 15:23 UTCEPSS rescore
  32. 2026-07-20 17:06 UTCEPSS rescore
  33. 2026-07-19 14:29 UTCEPSS rescore
  34. 2026-07-19 14:29 UTCEPSS rescore
  35. 2026-07-19 02:27 UTCEPSS rescore
  36. 2026-07-19 02:27 UTCEPSS rescore
  37. 2026-07-18 10:03 UTCEPSS rescore
  38. 2026-07-18 10:03 UTCEPSS rescore
  39. 2026-07-16 17:01 UTCEPSS rescore
  40. 2026-07-15 16:56 UTCEPSS rescore
  41. 2026-07-15 16:56 UTCEPSS rescore
  42. 2026-07-15 16:19 UTCOSV refresh
  43. 2026-07-15 01:58 UTCEPSS rescore
  44. 2026-07-15 01:58 UTCEPSS rescore
  45. 2026-07-13 22:28 UTCEPSS rescore
  46. 2026-07-13 22:28 UTCEPSS rescore
  47. 2026-07-13 06:11 UTCEPSS rescore
  48. 2026-07-13 06:11 UTCEPSS rescore
  49. 2026-07-12 05:45 UTCEPSS rescore
  50. 2026-07-11 08:26 UTCEPSS rescore
  51. 2026-07-11 08:25 UTCEPSS rescore
  52. 2026-07-09 19:08 UTCEPSS rescore
  53. 2026-07-09 19:08 UTCEPSS rescore
  54. 2026-07-08 15:13 UTCEPSS rescore
  55. 2026-07-06 16:26 UTCEPSS rescore
  56. 2026-07-06 16:26 UTCEPSS rescore
  57. 2026-07-06 02:21 UTCEPSS rescore
  58. 2026-07-05 02:29 UTCEPSS rescore
  59. 2026-07-04 06:29 UTCEPSS rescore
  60. 2026-07-02 16:59 UTCEPSS rescore
  61. 2026-07-01 15:04 UTCEPSS rescore
  62. 2026-06-30 23:21 UTCEPSS rescore
  63. 2026-06-30 23:21 UTCEPSS rescore
  64. 2026-06-29 14:05 UTCEPSS rescore
  65. 2026-06-29 14:05 UTCEPSS rescore
  66. 2026-06-28 14:06 UTCEPSS rescore
  67. 2026-06-28 14:06 UTCEPSS rescore
  68. 2026-06-28 04:55 UTCEPSS rescore
  69. 2026-06-28 04:55 UTCEPSS rescore
  70. 2026-06-27 16:34 UTCOSV refresh
  71. 2026-06-27 03:07 UTCEPSS rescore
  72. 2026-06-27 03:07 UTCEPSS rescore
  73. 2026-06-25 13:48 UTCEPSS rescore
  74. 2026-06-25 13:48 UTCEPSS rescore
  75. 2026-06-24 14:04 UTCEPSS rescore

Frequently asked(5)

What is CVE-2023-35936?
CVE-2023-35936 is a medium vulnerability published on July 5, 2023. Pandoc is a Haskell library for converting from one markup format to another, and a command-line tool that uses this library. Starting in version 1.13 and prior to version 3.1.4, Pandoc is susceptible to an arbitrary file write vulnerability, which can be triggered by providing a specially crafted…
When was CVE-2023-35936 disclosed?
CVE-2023-35936 was first published in the National Vulnerability Database on July 5, 2023, with the most recent update on February 13, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-35936 actively exploited?
CVE-2023-35936 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 70.1% of all scored CVEs.
What is the CVSS score of CVE-2023-35936?
CVE-2023-35936 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2023-35936?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-35936, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-35936

Explore →

Is Your Infrastructure Affected by CVE-2023-35936?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.