CVE-2026-126063: Mutation XSS through `noscript` content in Nokogiri's HTML5 serializer
Affects nokogiriSource GCVE Database
Not known to be exploited · CVSS 2.3 Low : upgrade to 1.19.5 when convenient.
Data as of 10 Nov 2026, 21:07 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 2.3 |
|---|
- Patch
- Available – fixed in 1.19.5
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 10 Nov 2026.
What to do
Upgrade nokogiri to 1.19.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| RubyGemsnokogiri | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to Nokogiri version 1.19.5 or later, where the issue is fixed. For earlier versions or as an additional precaution, applications that sanitize HTML and allow noscript elements should parse with the parse_noscript_content_as_text option set to true, or remove noscript elements entirely. This workaround is recommended even on fixed versions because some noscript content is serialized unescaped as per the HTML standard.
Description
Nokogiri's HTML5 serializer prior to version 1.19.5 did not properly escape text inside noscript elements or angle brackets inside attribute values. This flaw could lead to mutation cross-site scripting (XSS) when sanitized HTML containing noscript elements is serialized and rendered by browsers with scripting enabled. The issue affects only the C extension versions (CRuby and TruffleRuby) and not JRuby. The vulnerability is rated low severity with a CVSS score of 2.3. The maintainers recommend upgrading to Nokogiri 1.19.5 or later and using the parse_noscript_content_as_text option or removing noscript elements as mitigation.
References
- github.com/sparklemotion/nokogiri/security/advisories/GHSA-4p39-36wj-23h4 (opens in a new tab)
- github.com/sparklemotion/nokogiri/pull/3752 (opens in a new tab)
- github.com/sparklemotion/nokogiri/commit/3e84df6ff7ab4d78f446e3a415430bd69a055d32 (opens in a new tab)
- github.com/sparklemotion/nokogiri/commit/c6c0bffbdcd194694995acafeeed27326b0805f8 (opens in a new tab)
- github.com/rubysec/ruby-advisory-db/blob/master/gems/nokogiri/GHSA-4p39-36wj-23h4.yml (opens in a new tab)
- github.com/sparklemotion/nokogiri (opens in a new tab)
- github.com/sparklemotion/nokogiri/releases/tag/v1.19.5 (opens in a new tab)