Skip to main content
CVE-2026-133244VulnerabilityPublished

parse5-html-rewriting-stream 7.0.0 before 8.1.1 contains a cross-site scripting vulnerability in

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-133244· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 8.1.1 when convenient.

Data as of 19 Nov 2026, 19:34 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.05.3
CNA (VulnCheck)CVSS 3.16.1
Patch
Available – fixed in 8.1.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade parse5 to 8.1.1.

Affected software

ProductAffectedFixed in
inikulinparse5Affected
  • >=7.0.0 <8.1.1
Fixed in
  • 8.1.1
npmparse5pkg:npm/parse5Other threatsAffected
  • >=7.0.0 <8.1.1
Fixed in
  • 8.1.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in parse5-html-rewriting-stream version 8.1.1 and later. Users should upgrade to version 8.1.1 or newer to remediate this vulnerability. No vendor advisory content was provided to indicate alternative mitigations or temporary workarounds.

Description

parse5-html-rewriting-stream versions 7.0.0 up to but not including 8.1.1 contain a cross-site scripting (XSS) vulnerability in the RewritingStream#emitText function. This vulnerability arises because escaping is skipped based on a stale lastStartTagName, allowing attackers to inject entity-encoded markup after closed script or style elements. This can bypass filters relying on RewritingStream and enable script execution in users' browsers.

References

Community reviews

Loading reviews…