PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-44829 gotenberg CVE debrief

CVE-2026-44829 is a high-severity vulnerability in Gotenberg, a Docker-powered stateless API for PDF files. The issue, fixed in version 8.33.0, allows a remote attacker to write arbitrary files on a downstream Windows system when a user or process extracts a returned archive. The vulnerability arises from filename handling in pkg/modules/api/context.go, which does not properly sanitize Windows-style parent directory components, enabling an attacker to submit a malicious filename and cause file writes outside the intended extraction directory.

Vendor
gotenberg
Product
Unknown
CVSS
HIGH 8.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-19
Original CVE updated
2026-09-09
Advisory published
2026-08-19
Advisory updated
2026-09-09

Who should care

Defenders responsible for Gotenberg deployments, particularly those using Windows systems downstream of the API, should assess exposure and apply the fix. The vulnerability can lead to arbitrary file writes on downstream Windows systems when a user or process extracts a returned archive.

Why it matters

CVE-2026-44829 is a high-severity vulnerability in Gotenberg that allows arbitrary file writes on downstream Windows systems. Defenders should prioritize verifying exposure, applying the fix, and monitoring for potential exploitation attempts.

  • Arbitrary file writes on downstream Windows systems when extracting archives.
  • Potential for exploitation leading to unauthorized file creation or modification.
  • Need for verification of Gotenberg version and exposure to vulnerable endpoints.
  • Prioritization of upgrading to version 8.33.0 to prevent exploitation.

Technical summary

The vulnerability in Gotenberg arises from improper filename handling in pkg/modules/api/context.go. When a multipart filename containing Windows-style parent directory components is submitted, it survives sanitization and can be used to write files outside the intended extraction directory in a returned archive. This issue affects Gotenberg versions 8.32.0 and earlier and is fixed in version 8.33.0.

Defensive priority

Defenders should prioritize verifying exposure and applying the fix, as the vulnerability can lead to arbitrary file writes on downstream Windows systems.

Recommended defensive actions

  • Verify if the system uses Gotenberg version 8.32.0 or earlier and prioritize upgrading to version 8.33.0.
  • Review and sanitize filenames used in upload and download processes to prevent malicious file writes.
  • Implement additional monitoring and logging to detect potential exploitation attempts.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. The Gotenberg GitHub repository contains references to the issue and the fix.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-44829 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-44829

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-44829 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-44829

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.