Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The sanitize-html npm package, versions before 2.18.0, is affected. Its handling of nonTextTags (such as noscript-adjacent content) ends the discard region early when htmlparser2 emits an implied close, so content inside a noscript element can be passed through as ordinary markup. An attacker who can supply HTML to be sanitized can get elements into the output that a browser with scripting enabled would not render, and the source notes this is a parsing mismatch rather than a full exploit chain. The fix is to upgrade to sanitize-html 2.18.0 or later, which is listed as the fixed version.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.3 | Medium | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0043, the 37th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 13:33 UTC First seen by agentprime
- 31 Oct 2026, 13:33 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-x3q4-9hxx-gx8m
- OSV: GHSA-x3q4-9hxx-gx8m
- github.com/apostrophecms/apostrophe/security/advisories/GHSA-x3q4-9hxx-gx8m
- github.com/apostrophecms/apostrophe/commit/9500b8b0e1d630d5e07fbb5fd2c25ed0943845ce
- github.com/apostrophecms/apostrophe/commit/f84fd41cbf6c22eb8d0008fc9c25df1f7130b350
- github.com/apostrophecms/apostrophe
- github.com/apostrophecms/apostrophe/releases/tag/[email protected]