CVE-2026-44829

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% 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, secondary
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

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

Gotenberg is a Docker-powered stateless API for PDF files. In 8.32.0 and earlier, filename handling in pkg/modules/api/context.go uses filepath.Base on Linux, which does not treat backslashes as path separators, so a multipart filename containing Windows-style parent directory components survives sanitization. The original filename flows through ctx.diskToOriginal and the multi-output PDF routes into archives.FilesFromDisk and archives.Zip.Archive as the generated zip entry name. A remote attacker can submit a name such as ........\Windows\System32\evil.pdf through an upload or an upstream downloadFrom Content-Disposition header, and a Windows archive extractor can write the resulting file outside the intended extraction directory. The affected paths include /forms/pdfengines/split and other multi-output PDF, LibreOffice, and conversion routes, and exploitation can cause arbitrary file writes on a downstream Windows system when a user or process extracts the returned archive. This issue is fixed in version 8.33.0.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

May 29, 2026

Last Modified

August 19, 2026

Advisory Details (4)

Auto-updated Aug 19, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

8.33.0

Patch available: gotenberg/gotenberg v8.33.0

https://github.com/gotenberg/gotenberg/releases/tag/v8.33.0
github_commit Patch Available

commit 93d010358537 (gotenberg/gotenberg)

Patch available: gotenberg/gotenberg v8.33.0 (contains commit 93d010358537)

https://github.com/gotenberg/gotenberg/commit/93d0103585372433e18b351bb16edf4c383932d3
generic

Nordic characters break loading · Issue #662 · gotenberg/gotenberg · GitHub

https://github.com/gotenberg/gotenberg/issues/662
github Patch Available🟡 PoC Available

Path traversal in zip entry name via Windows-style separators in upload filename · Advisory · gotenberg/gotenberg · GitHub

https://github.com/gotenberg/gotenberg/security/advisories/GHSA-hwc4-gmrw-5222

Vendor Advisories for CVE-2026-44829(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/gotenberg/gotenberg/v7
github.com/gotenberg/gotenberg/v88.33.0

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 18× 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.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 04:20 UTCEG score recompute
  11. 2026-08-23 14:12 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 15:09 UTCEG score recompute
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-19 19:22 UTCEG score recompute
  17. 2026-08-19 18:24 UTCEG score recompute
  18. 2026-08-19 15:32 UTCEG score recompute
  19. 2026-07-31 05:53 UTCEG score recompute
  20. 2026-07-27 09:08 UTCEG score recompute
  21. 2026-07-23 03:15 UTCEG score recompute
  22. 2026-06-14 23:18 UTCEPSS rescore
  23. 2026-06-12 23:12 UTCEPSS rescore
  24. 2026-05-29 17:20 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-44829?
CVE-2026-44829 is a high vulnerability published on May 29, 2026. Gotenberg is a Docker-powered stateless API for PDF files. In 8.32.0 and earlier, filename handling in pkg/modules/api/context.go uses filepath.Base on Linux, which does not treat backslashes as path separators, so a multipart filename containing Windows-style parent directory components survives…
When was CVE-2026-44829 disclosed?
CVE-2026-44829 was first published in the National Vulnerability Database on May 29, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44829 actively exploited?
CVE-2026-44829 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 69.8% of all scored CVEs.
What is the CVSS score of CVE-2026-44829?
CVE-2026-44829 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-44829?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44829, 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-2026-44829

Explore →

Is Your Infrastructure Affected by CVE-2026-44829?

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