Path Traversal in libreoffice-convert (CVE-2026-54732)
Summary
Path traversal in libreoffice-convert (CVE-2026-54732). Data can be tampered with by attackers. Exploitable via path.basename. Mitigation: upgrade to 1.8.2 or later.
Original description
The description as published by the source.
Impact
options.fileName is used to build a filesystem path
(path.join(tempDir.name, fileName)) and the caller-supplied document buffer is
written there, but fileName is never reduced to a base name. A fileName containing
"../" escapes the temporary directory, so a caller can write arbitrary content to an
arbitrary path the process can write to (e.g. ~/.ssh/authorized_keys, an /etc/cron.d
entry, or a web root).
Patches
Version 1.8.2 uses path.basename on filename to make sure the temp directory can not be escaped.
Workarounds
Make sure you supply the filename yourself and don't have it user supplied or use path.basename on filename before using it in libreoffice-convert.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
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 CVE-2026-54732 has been found in libreoffice-convert.
Attackers can target a specific entry point like path.basename over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade libreoffice-convert to 1.8.2 or later.
If unsure, ask your IT team or search "libreoffice-convert CVE-2026-54732" on the vendor's site.
CVE-2026-54732 (libreoffice-convert) — CWE-22 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: path.basename / filename
Patched: 1.8.2 — apply immediately
Workaround: Make sure you supply the filename yourself and don't have it user supplied or use path.basename on filename before using it in libreoffice-convert.
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.
Path traversal (CWE-22) exists in libreoffice-convert. Attackers reach the vulnerable code path via path.basename.
Check the vendor advisory for the affected versions of libreoffice-convert. Attack surface: path.basename / filename.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 1.8.2.
Workaround: Make sure you supply the filename yourself and don't have it user supplied or use path.basename on filename before using it in libreoffice-convert.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'libreoffice-convert' . 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-convert' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
libreoffice-convertを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Make sure you supply the filename yourself and don't have it user supplied or use `path.basename` on `filename` before using it in `libreoffice-convert`.パッチが適用されるまでの応急処置として、Make sure you supply the filename yourself and don't have it user supplied or use
path.basenameonfilenamebefore using it inlibreoffice-convert. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade libreoffice-convert to 1.8.2ステージング環境で 1.8.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com