Vulnerability in libredwg (OSV-2026-995)

Summary

vulnerability in libredwg (OSV-2026-995). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `5c707f7c5f748b060eb0e607f045ef617ea75e16, 30f4304649433c690a62d6d0940c98a0371fda96, db9e5f65c3bb6f26152ebdd9ea83b5a85f907e04, f7e92baa1bfdf38183383b2313bf7a266749ae39, 359300104fa0c8c60e95426da2d82e170e2624e8` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **OSV-2026-995** has been found in libredwg. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade libredwg to **5c707f7c5f748b060eb0e607f045ef617ea75e16, 30f4304649433c690a62d6d0940c98a0371fda96, db9e5f65c3bb6f26152ebdd9ea83b5a85f907e04, f7e92baa1bfdf38183383b2313bf7a266749ae39, 359300104fa0c8c60e95426da2d82e170e2624e8** or later. If unsure, ask your IT team or search "libredwg OSV-2026-995" on the vendor's site.

OSV-2026-995 (libredwg) — Patched: `5c707f7c5f748b060eb0e607f045ef617ea75e16, 30f4304649433c690a62d6d0940c98a0371fda96, db9e5f65c3bb6f26152ebdd9ea83b5a85f907e04, f7e92baa1bfdf38183383b2313bf7a266749ae39, 359300104fa0c8c60e95426da2d82e170e2624e8` — apply immediately Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

**A vulnerability** (unclassified) exists in libredwg.

📍 Affected scope

libredwg — .

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **5c707f7c5f748b060eb0e607f045ef617ea75e16, 30f4304649433c690a62d6d0940c98a0371fda96, db9e5f65c3bb6f26152ebdd9ea83b5a85f907e04, f7e92baa1bfdf38183383b2313bf7a266749ae39, 359300104fa0c8c60e95426da2d82e170e2624e8**.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'libredwg' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'libredwg' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `libredwg` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade libredwg to 5c707f7c5f748b060eb0e607f045ef617ea75e16, 30f4304649433c690a62d6d0940c98a0371fda96, db9e5f65c3bb6f26152ebdd9ea83b5a85f907e04, f7e92baa1bfdf38183383b2313bf7a266749ae39, 359300104fa0c8c60e95426da2d82e170e2624e8
```
ステージング環境で 5c707f7c5f748b060eb0e607f045ef617ea75e16, 30f4304649433c690a62d6d0940c98a0371fda96, db9e5f65c3bb6f26152ebdd9ea83b5a85f907e04, f7e92baa1bfdf38183383b2313bf7a266749ae39, 359300104fa0c8c60e95426da2d82e170e2624e8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

OSS-Fuzz libredwg

[{"repo":"https:\/\/github.com\/LibreDWG\/libredwg","type":"GIT","events":[{"introduced":"fdf42300c049bd5b791668362873a02b5ee3ce2b"},{"fixed":"5c707f7c5f748b060eb0e607f045ef617ea75e16"},{"fixed":"30f4304649433c690a62d6d0940c98a0371fda96"},{"fixed":"db9e5f65c3bb6f26152ebdd9ea83b5a85f907e04"},{"fixed":"f7e92baa1bfdf38183383b2313bf7a266749ae39"},{"fixed":"359300104fa0c8c60e95426da2d82e170e2624e8"}]}]

References

report https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=528859714