libreoffice-convert vulnerable to path traversal / arbitrary file write

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

EPSS

• CVE-2026-54732: 0.42% estimated exploitation activity in the next 30 days; percentile 35.98 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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/authorizedkeys, 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.

Published by the source

27 Aug 2026, 17:23 UTC

Last modified by the source

27 Aug 2026, 17:23 UTC

Source last checked

26 Oct 2026, 13:01 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gmxc-r82q-347r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54732

Advisory: libreoffice-convert vulnerable to path traversal / arbitrary file write
IDs: CVE-2026-54732, GHSA-gmxc-r82q-347r
Record: https://patchnext.com/advisories/cve-2026-54732 (revision 1, source checked 26 Oct 2026, 13:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: libreoffice-convert 1.8.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm libreoffice-convert: affected < 1.8.2; fixed in 1.8.2

## Suggested inspection (read-only)
- `npm ls libreoffice-convert --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on libreoffice-convert.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gmxc-r82q-347r (GitHub-reviewed advisory GHSA-gmxc-r82q-347r lists affected ranges: npm libreoffice-convert >=0 <1.8.2)

Commands are suggestions: review each one before running it.