docconv vulnerable to Memory Allocation with Excessive Size ValueGHSA-qvx2-59g8-8hph
MEDIUMFix: sajari/docconv#111GHSA-qvx2-59g8-8hph is a medium-severity (CVSS 6.5) CWE-789 vulnerability in github.com/sajari/docconv. A fix is available for github.com/sajari/docconv — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/sajari/docconv🐹code.sajari.com/docconvReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
A vulnerability was found in docconv up to 1.2.0 and classified as problematic. This issue affects the function ConvertDocx/ConvertODT/ConvertPages/ConvertXML/XMLToText. The manipulation leads to uncontrolled memory allocation. The attack may be initiated remotely. Upgrading to version 1.2.1 is able to address this issue. The name of the patch is 42bcff666855ab978e67a9041d0cdea552f20301. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-216779.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/sajari/docconv | all versions | 1.2.1go get github.com/sajari/docconv@v1.2.1 |
| 🐹Go | code.sajari.com/docconv | all versions | 1.2.1go get code.sajari.com/docconv@v1.2.1 |
Affected Products
docconvsearchDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/sajari/docconv, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/sajari/docconv to 1.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qvx2-59g8-8hph is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is GHSA-qvx2-59g8-8hph in your dependencies?
Find it across Go, including transitive dependencies.