Skip to content

Update dependency nokogiri to v1.19.1 [SECURITY]#8886

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/rubygems-nokogiri-vulnerability
Open

Update dependency nokogiri to v1.19.1 [SECURITY]#8886
renovate[bot] wants to merge 1 commit intomainfrom
renovate/rubygems-nokogiri-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Jul 22, 2025

This PR contains the following updates:

Package Change Age Confidence
nokogiri 1.18.81.19.1 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

GitHub Vulnerability Alerts

GHSA-353f-x4gh-cqq8

Summary

Nokogiri v1.18.9 patches the vendored libxml2 to address CVE-2025-6021, CVE-2025-6170, CVE-2025-49794, CVE-2025-49795, and CVE-2025-49796.

Impact and severity

CVE-2025-6021

A flaw was found in libxml2's xmlBuildQName function, where integer overflows in buffer size calculations can lead to a stack-based buffer overflow. This issue can result in memory corruption or a denial of service when processing crafted input.

NVD claims a severity of 7.5 High (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)

Fixed by applying https://gitlab.gnome.org/GNOME/libxml2/-/commit/17d950ae

CVE-2025-6170

A flaw was found in the interactive shell of the xmllint command-line tool, used for parsing XML files. When a user inputs an overly long command, the program does not check the input size properly, which can cause it to crash. This issue might allow attackers to run harmful code in rare configurations without modern protections.

NVD claims a severity of 2.5 Low (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L)

Fixed by applying https://gitlab.gnome.org/GNOME/libxml2/-/commit/5e9ec5c1

CVE-2025-49794

A use-after-free vulnerability was found in libxml2. This issue occurs when parsing XPath elements under certain circumstances when the XML schematron has the <sch:name path="..."/> schema elements. This flaw allows a malicious actor to craft a malicious XML document used as input for libxml, resulting in the program's crash using libxml or other possible undefined behaviors.

NVD claims a severity of 9.1 Critical (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H)

Fixed by applying https://gitlab.gnome.org/GNOME/libxml2/-/commit/81cef8c5

CVE-2025-49795

A NULL pointer dereference vulnerability was found in libxml2 when processing XPath XML expressions. This flaw allows an attacker to craft a malicious XML input to libxml2, leading to a denial of service.

NVD claims a severity of 7.5 High (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)

Fixed by applying https://gitlab.gnome.org/GNOME/libxml2/-/commit/62048278

CVE-2025-49796

A vulnerability was found in libxml2. Processing certain sch:name elements from the input XML file can trigger a memory corruption issue. This flaw allows an attacker to craft a malicious XML input file that can lead libxml to crash, resulting in a denial of service or other possible undefined behavior due to sensitive data being corrupted in memory.

NVD claims a severity of 9.1 Critical (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H)

Fixed by applying https://gitlab.gnome.org/GNOME/libxml2/-/commit/81cef8c5

Affected Versions

  • Nokogiri < 1.18.9 when using CRuby (MRI) with vendored libxml2

Patched Versions

  • Nokogiri >= 1.18.9

Mitigation

Upgrade to Nokogiri v1.18.9 or later.

Users who are unable to upgrade Nokogiri may also choose a more complicated mitigation: compile and link Nokogiri against patched external libxml2 libraries which will also address these same issues.

References

Severity

Critical

GHSA-wx95-c6cv-8532

Summary

Nokogiri's CRuby extension fails to check the return value from xmlC14NExecute in the method Nokogiri::XML::Document#canonicalize and Nokogiri::XML::Node#canonicalize. When canonicalization fails, an empty string is returned instead of raising an exception. This incorrect return value may allow downstream libraries to accept invalid or incomplete canonicalized XML, which has been demonstrated to enable signature validation bypass in SAML libraries.

JRuby is not affected, as the Java implementation correctly raises RuntimeError on canonicalization failure.

Mitigation

Upgrade to Nokogiri >= 1.19.1.

Severity

The maintainers have assessed this as Medium severity. Nokogiri itself is a parsing library without a clear security boundary related to canonicalization, so the direct impact is that a method returns incorrect data on invalid input. However, this behavior was exploited in practice to bypass SAML signature validation in downstream libraries (see References).

Credit

This vulnerability was responsibly reported by HackerOne researcher d4d.

Severity
  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • ""
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the review:tech Request for technical review on the docs platform or processes. label Jul 22, 2025
@renovate renovate bot requested a review from a team as a code owner July 22, 2025 05:12
@renovate renovate bot added the review:tech Request for technical review on the docs platform or processes. label Jul 22, 2025
@netlify
Copy link
Copy Markdown

netlify bot commented Jul 22, 2025

Deploy Preview for kongdocs ready!

Name Link
🔨 Latest commit 3a90041
🔍 Latest deploy log https://app.netlify.com/projects/kongdocs/deploys/69cacab2a32a0f00084c60a9
😎 Deploy Preview https://deploy-preview-8886--kongdocs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
9 paths audited
Performance: 69 (🟢 up 7 from production)
Accessibility: 77 (🔴 down 10 from production)
Best Practices: 99 (no change from production)
SEO: 92 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@renovate renovate bot force-pushed the renovate/rubygems-nokogiri-vulnerability branch from 2f20877 to 9c4d278 Compare August 10, 2025 15:32
@renovate renovate bot changed the title Update dependency nokogiri to v1.18.9 [SECURITY] chore(deps): update dependency nokogiri to v1.18.9 [security] Sep 12, 2025
@renovate renovate bot force-pushed the renovate/rubygems-nokogiri-vulnerability branch from 9c4d278 to 4ea7ec9 Compare September 25, 2025 18:04
@renovate renovate bot changed the title chore(deps): update dependency nokogiri to v1.18.9 [security] chore(deps): update dependency nokogiri to v1.19.1 [security] Feb 19, 2026
@renovate renovate bot force-pushed the renovate/rubygems-nokogiri-vulnerability branch from 4ea7ec9 to 583487e Compare February 19, 2026 23:04
@renovate renovate bot changed the title chore(deps): update dependency nokogiri to v1.19.1 [security] chore(deps): update dependency nokogiri to v1.19.1 [security] - autoclosed Mar 27, 2026
@renovate renovate bot closed this Mar 27, 2026
@renovate renovate bot deleted the renovate/rubygems-nokogiri-vulnerability branch March 27, 2026 02:48
@renovate renovate bot changed the title chore(deps): update dependency nokogiri to v1.19.1 [security] - autoclosed chore(deps): update dependency nokogiri to v1.19.1 [security] Mar 30, 2026
@renovate renovate bot reopened this Mar 30, 2026
@renovate renovate bot force-pushed the renovate/rubygems-nokogiri-vulnerability branch 2 times, most recently from 583487e to 3a90041 Compare March 30, 2026 19:10
@renovate renovate bot changed the title chore(deps): update dependency nokogiri to v1.19.1 [security] Update dependency nokogiri to v1.19.1 [SECURITY] Apr 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

review:tech Request for technical review on the docs platform or processes.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants