UBUNTU-CVE-2026-126063: Medium severity ubuntu/ruby-nokogiri vulnerability

Published Nov 12, 2026
·
Updated

Nokogiri is an open source XML and HTML library for the Ruby programming language. From 1.12.0 until 1.19.5, the C extension on CRuby and TruffleRuby has a Nokogiri::HTML5 serializer that does not escape text inside noscript elements or angle brackets inside attribute values. When an application sanitizes untrusted HTML with the default parsing options, allows noscript, and sends serialized output to a scripting-enabled browser, the browser can parse markup that Nokogiri did not produce, enabling mutation cross-site scripting. Using parsenoscriptcontentastext: true is the recommended workaround, not the vulnerable default. JRuby is not affected because it does not implement Nokogiri::HTML5. This issue is fixed in version 1.19.5.

Affected Software

8 affected components
ubuntu/ruby-nokogiri*
ubuntu/ruby-nokogiri*
ubuntu/ruby-nokogiri*
ubuntu/ruby-nokogiri*
ubuntu/ruby-nokogiri*
ubuntu/ruby-nokogiri*
ubuntu/ruby-nokogiri*
ubuntu/ruby-nokogiri*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Nokogiri to a version that resolves this vulnerability.

    Fixed in 1.19.5
  2. Configuration

    Set parse_noscript_content_as_text to true when parsing HTML as a workaround.

    Nokogiri::HTML5 serializer parse_noscript_content_as_text = true

Event History

Nov 12, 2026
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which deployments are affected?

Deployments using Nokogiri’s C extension on CRuby or TruffleRuby are affected from version 1.12.0 through 1.19.4. JRuby is not affected because it does not implement Nokogiri::HTML5.

2

What conditions are needed for exploitation?

An application must sanitize untrusted HTML using the default parsing options, permit noscript elements, and send the serialized result to a browser with scripting enabled. Under those conditions, an attacker may cause the browser to parse markup that Nokogiri did not produce.

3

Is the default configuration vulnerable?

Yes. The vulnerable behavior occurs when untrusted HTML is sanitized with Nokogiri’s default parsing options and noscript is allowed.

4

What can be done if upgrading is not immediately possible?

Use parse_noscript_content_as_text: true when parsing. This is the recommended workaround and is not the vulnerable default.

5

What version fixes the issue?

The issue is fixed in Nokogiri version 1.19.5.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203