parse5 HTML Rewriting Stream cross-site scripting in RewritingStream#emitText
- Exploited
- No known exploitation
- Fix
- Fixed in 8.1.1
- Who is exposed
- Not reported
Summary
The parse5-html-rewriting-stream package, from the parse5 product, has a cross-site scripting flaw in its RewritingStream#emitText method, which skips escaping based on a stale tag name after a closed script or style element. A remote attacker who does not need to log in can place entity-encoded markup to bypass RewritingStream-based filters and run script in users' browsers, but a user must take an action for the attack to work.
Written by a model
Original description
parse5-html-rewriting-stream 7.0.0 before 8.1.1 contains a cross-site scripting vulnerability in RewritingStream#emitText, which skips escaping based on a stale lastStartTagName. Attackers can place entity-encoded markup after a closed script or style element to bypass RewritingStream-based filters and execute script in users' browsers.
What to do
Upgrade to a fixed version: 8.1.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133244 (parse5-html-rewriting-stream 7.0.0 before 8.1.1 XSS via RewritingStream#emitText), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133244 (entry last updated 2026-11-19):
Affected:
- npm package parse5-html-rewriting-stream: from 7.0.0, fixed in 8.1.1
Fixed versions: 8.1.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133244 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133244 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/inikulin/parse5/pull/1921
- https://github.com/inikulin/parse5/commit/e02abba4aa177b70a3a26cf90f6d62cd3ef8c44a
- https://github.com/inikulin/parse5/releases/tag/v8.1.1
- https://github.com/inikulin/parse5/blob/v8.1.0/packages/parse5-html-rewriting-stream/lib/index.ts#L137-L145
- https://github.com/inikulin/parse5
- https://www.vulncheck.com/advisories/parse5-html-rewriting-stream-7.0.0-before-8.1.1-xss-via-rewritingstream-emittext
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133244
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133244"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach10/20Affects npm packages
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 37 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 8
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133244 |
| Record | NVD · CVE-2026-133244 |
| Other links 6 | |
| Patch | GitHub · inikulin/parse5 · Pull request #1921 |
| Patch | GitHub · inikulin/parse5 · Commit e02abba4 |
| Repository | GitHub · inikulin/parse5 · Release v8.1.1 |
| Repository | GitHub · inikulin/parse5 · packages/parse5-html-rewriting-stream/lib/index.ts · L137-L145 |
| Repository | GitHub · inikulin/parse5 · Repository |
| Link | vulncheck.com · advisories/parse5-html-rewriting-stream-7.0.0-before-8.1.1-xss-via-rewritingstream-emittext |
Questions about CVE-2026-133244
Is CVE-2026-133244 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133244?
parse5-html-rewriting-stream (npm): from 7.0.0 before 8.1.1.
Source: cve.now feed data
How do I fix CVE-2026-133244?
Upgrade to a fixed version: 8.1.1.
Source: cve.now feed data
Related
- CVE-2026-133245parse5 7.0.0 before 8.1.1 Denial of Service via Preprocessor#_processSurrogate
- CVE-2026-22308Missing authentication for critical function leading to reflected cross-site scripting in JTL-Shop
- CVE-2026-22309Stored cross-site scripting in JTL-Shop
- CVE-2026-130158RepoManager: Stored XSS via host-reported package metadata
- CVE-2026-131260Cross-Site Scripting (XSS) through the REST API in Splunk SOAR
- CVE-2026-131258Stored Cross-Site Scripting (XSS) through the REST API in Splunk SOAR
No corrections so far. Something wrong on this page? Report an error.