CVE-2025-61154
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 · uneditedHeap buffer overflow vulnerability in LibreDWG versions v0.13.3.7571 up to v0.13.3.7835 allows a crafted DWG file to cause a Denial of Service (DoS) via the function decompress_R2004_section at decode.c.
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 confidenceA heap buffer overflow vulnerability exists in LibreDWG's decompress_R2004_section function in decode.c. When processing specially crafted DWG files, the function fails to properly validate buffer sizes during R2004 section decompression, allowing an attacker to overflow the heap buffer and cause a denial of service.
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>= 0.13.3.7571, <= 0.13.3.7835CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 if LibreDWG is installedRun 'dwg2dxf --version' or 'redwg --version' from command line. Alternatively, check your package manager (dpkg -l | grep libredwg, rpm -qa | grep libredwg, or brew list libredwg).Affected if LibreDWG is not installed or no version output is returned, then you are not using this product.
-
Verify the exact version numberCompare the output version against the affected range >= 0.13.3.7571 and <= 0.13.3.7835. Look for versions like 0.13.3.7571, 0.13.3.7600, 0.13.3.7800, or 0.13.3.7835.Affected if Your installed version falls within 0.13.3.7571 through 0.13.3.7835 inclusive.
-
Determine if your application uses the decode functionalityCheck if any software on your system links to libredwg (ldd /path/to/your/application | grep redwg, or review application dependencies). The vulnerability is in decompress_R2004_section in decode.c.Affected if Applications process DWG files using LibreDWG's decoding functions.
-
Identify if DWG file processing is actively usedReview logs, file access patterns, or user workflows to see if DWG files from external or untrusted sources are being processed. Check application configs for DWG import/validation features.Affected if Your system processes DWG files, especially from external or untrusted sources.
You are affected if LibreDWG version 0.13.3.7571 through 0.13.3.7835 is installed and your system processes DWG files using the decode functionality.
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.
From vendor dataUpgrade LibreDWG to version v0.13.3.7836 or later. Until a patch is available, restrict processing of DWG files from untrusted sources and implement file type validation.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61154 — 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-2025-61154 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