Vulnerability in libreoffice (UBUNTU-CVE-2026-6039)
Summary
Vulnerability in libreoffice (UBUNTU-CVE-2026-6039). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1:7.3.7-0ubuntu0.22.04.12 or later.
Original description
The description as published by the source.
LibreOffice can import drawings in the DXF format used by CAD software. A heap buffer overflow existed when importing a DXF polyline. The point count taken from the file was truncated to a 16-bit value when the point buffer was sized, while the full count was used to fill it, so a polyline whose point count exceeded the 16-bit range was written past the end of the buffer. In fixed versions such oversized polylines are rejected.
Source: OSV.dev (Open Source Vulnerabilities) OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as UBUNTU-CVE-2026-6039 has been found in libreoffice.
Risk of unauthorized operations or information disclosure.
What to do: upgrade libreoffice to 1:7.3.7-0ubuntu0.22.04.12 or later.
If unsure, ask your IT team or search "libreoffice UBUNTU-CVE-2026-6039" on the vendor's site.
UBUNTU-CVE-2026-6039 (libreoffice)
Patched: 1:7.3.7-0ubuntu0.22.04.12 — 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.
A vulnerability (unclassified) exists in libreoffice.
Check the vendor advisory for the affected versions of libreoffice.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1:7.3.7-0ubuntu0.22.04.12.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'libreoffice' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'libreoffice' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
libreofficeを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade libreoffice to 1:7.3.7-0ubuntu0.22.04.12ステージング環境で 1:7.3.7-0ubuntu0.22.04.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory ubuntu.com
- report ubuntu.com
- report cve.org
- report libreoffice.org