odf-kit has HTML injection leading to XSS in odsToHtml() via unescaped style attribute values
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (odf-kit 0.14.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm odf-kit
- Affected
- >= 0.9.8, < 0.14.2
- Fixed in
- 0.14.2
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-2rqm-h6hv-g79v lists affected ranges: npm odf-kit >=0.9.8 <0.14.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-2rqm-h6hv-g79v lists affected ranges: npm odf-kit >=0.9.8 <0.14.2 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- 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.
Source description
As published by the source; long descriptions are shortened.
Summary ODF style values are interpolated into style="..." attributes without HTML-escaping in odf-kit's ODS to-HTML renderer (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 .ods file wherever the rendered output is inserted as HTML, which is the documented purpose of the function. Details Two emission sites in src/ods/to-html/html-renderer.ts (before 0.14.0, src/ods-reader/html-renderer.ts) write document-controlled values into a style attribute without escaping: - Cell style. buildInlineStyle() assembles a CSS string from the cell's formatting properties (fo:color, fo:font-size, fo:font-family, fo:background-color, fo:text-align, etc.) with no escaping, and renderCell emits it raw as the cell's style attribute. - Row height. row.height (from style:row-height) is emitted raw into the row element's style attribute. The same…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-2rqm-h6hv-g79v
- Revision 2 · amended ·
Amended from osv record GHSA-2rqm-h6hv-g79v
- Revision 1 · created ·
Published from ghsa record GHSA-2rqm-h6hv-g79v
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-2rqm-h6hv-g79v Advisory: odf-kit has HTML injection leading to XSS in odsToHtml() via unescaped style attribute values IDs: GHSA-2rqm-h6hv-g79v Record: https://patchnext.com/advisories/ghsa-2rqm-h6hv-g79v (revision 3, source checked 26 Oct 2026, 13:07 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.9.8, < 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-2rqm-h6hv-g79v (GitHub-reviewed advisory GHSA-2rqm-h6hv-g79v lists affected ranges: npm odf-kit >=0.9.8 <0.14.2) - Verified: https://osv.dev/vulnerability/GHSA-2rqm-h6hv-g79v (OSV record GHSA-2rqm-h6hv-g79v lists affected ranges: npm odf-kit >=0.9.8 <0.14.2 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…