odf-kit: HTML injection leading to XSS in odtToHtml() and odsToHtml() via unescaped style attribute values

Exploitation

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

CVSS

6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary ODF style attribute values are interpolated into style="..." attributes without HTML-escaping in both of odf-kit's to-HTML renderers (odtToHtml and odsToHtml). A double-quote character inside an attacker-controlled style value breaks out of the attribute, allowing arbitrary HTML/attribute injection — and therefore script execution (XSS) — from a crafted .odt or .ods file wherever the rendered output is inserted as HTML, which is the documented purpose of both functions. Details ODT renderer (src/odt/to-html/html-renderer.ts) The renderer has an escapeHtml() helper and applies it consistently to text content and to attribute values — href, src, alt, id, data-author, data-date, citation text all go through it. The inline CSS strings do not. In renderTextSpan (dist/odt/to-html/html-renderer.js:195): The value of e.g. fo:color is copied from the document into style.fontColor verbatim by the parser (extractSpanStyle, read/parser.js:348), then concatenated raw into the attribute. A…

Published by the source

4 Nov 2026, 16:14 UTC

Last modified by the source

4 Nov 2026, 16:14 UTC

Source last checked

4 Nov 2026, 16:55 UTC

1. Revision 1 · created · 4 Nov 2026

   Published from ghsa record GHSA-3cgg-c5pp-57h6

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

# Patch Next advisory brief: CVE-2026-113787

Advisory: odf-kit: HTML injection leading to XSS in odtToHtml() and odsToHtml() via unescaped style attribute values
IDs: CVE-2026-113787, GHSA-3cgg-c5pp-57h6
Record: https://patchnext.com/advisories/cve-2026-113787 (revision 1, source checked 4 Nov 2026, 16:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: odf-kit 0.14.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm odf-kit: affected >= 0.6.0, < 0.14.2; fixed in 0.14.2

## Suggested inspection (read-only)
- `npm ls odf-kit --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 odf-kit.
- 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-3cgg-c5pp-57h6 (GitHub-reviewed advisory GHSA-3cgg-c5pp-57h6 lists affected ranges: npm odf-kit >=0.6.0 <0.14.2)

Commands are suggestions: review each one before running it.