CVE-2026-35458
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGotenberg is an API for converting document formats. In 8.29.1 and earlier, Gotenberg uses dlclark/regexp2 to compile user-supplied scope patterns without setting a proper timeout. Users with access to features using this logic can hang workers indefinitely.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGotenberg versions 8.29.1 and earlier use the dlclark/regexp2 library to compile user-supplied scope patterns (regular expressions) without implementing a timeout mechanism. Attackers with access to affected features can supply malicious regex patterns that cause the regexp2 compilation to hang indefinitely, effectively denying service by hanging worker processes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 8.29.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Gotenberg versionQuery the Gotenberg health endpoint (e.g., curl http://<host>/health) or inspect the container image: docker inspect <container> | grep -i gotenbergAffected if Version returned or embedded is 8.29.1 or earlier (< 8.29.1)
-
Identify if scope/regex patterns are accepted by APIReview API documentation or capture live traffic to determine if any endpoint accepts a 'scope' parameter that gets compiled as a regex patternAffected if The API accepts scope parameter values from users that are processed as regexp2 patterns
-
Confirm authenticated users can submit patternsCheck the authentication configuration and endpoint permissions to see if authenticated users can access the scope pattern functionalityAffected if Authenticated users have access to API endpoints that process scope/regex patterns
-
Check if regexp2 library is used without timeoutReview application dependencies (go.mod, vendor folder, or binary analysis) for dlclark/regexp2 usage in scope pattern compilation codeAffected if The codebase uses dlclark/regexp2 to compile user-supplied patterns without a timeout mechanism
You are affected if Gotenberg version is below 8.29.1 AND authenticated users can submit scope/regex patterns to the API that get compiled by the regexp2 library without timeout protection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped8.29.1
Implement a timeout context around all regexp2 compilation operations, or upgrade to a patched version once available, to prevent unbounded regex processing.
8.29.1
- 1. Identify the current Gotenberg version running in your environment
- 2. Backup all Gotenberg configuration files and any persistent data
- 3. Upgrade Gotenberg to version 8.29.1 or later
- 4. Verify the upgrade by checking the new version number
- 5. Test that the API functionality remains operational
- 6. Monitor worker processes to confirm the timeout fix is effective
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35458 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35458 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data