# GHSA-5w6v-399v-w3cc: Nokogiri updates packaged libxml2 to v2.13.8 to resolve CVE-2025-32414 and CVE-2025-32415


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Apr 2025

## What is GHSA-5w6v-399v-w3cc?

GHSA-5w6v-399v-w3cc is a vulnerability in nokogiri, published on 21 Apr 2025. 

### Official description

## Summary

Nokogiri v1.18.8 upgrades its dependency libxml2 to [v2.13.8](https://gitlab.gnome.org/GNOME/libxml2/-/releases/v2.13.8).

libxml2 v2.13.8 addresses:

- CVE-2025-32414
  - described at https://gitlab.gnome.org/GNOME/libxml2/-/issues/889
- CVE-2025-32415
  - described at https://gitlab.gnome.org/GNOME/libxml2/-/issues/890

## Impact

### CVE-2025-32414: No impact

In libxml2 before 2.13.8 and 2.14.x before 2.14.2, out-of-bounds memory access can occur in the Python API (Python bindings) because of an incorrect return value. This occurs in xmlPythonFileRead and xmlPythonFileReadRaw because of a difference between bytes and characters.

**There is no impact** from this CVE for Nokogiri users.

### CVE-2025-32415: Low impact

In libxml2 before 2.13.8 and 2.14.x before 2.14.2, xmlSchemaIDCFillNodeTables in xmlschemas.c has a heap-based buffer under-read. To exploit this, a crafted XML document must be validated against an XML schema with certain identity constraints, or a crafted XML schema must be used.

In the upstream issue, further context is provided by the maintainer:

> The bug affects validation against untrusted XML Schemas (.xsd) and validation of untrusted
> documents against trusted Schemas if they make use of xsd:keyref in combination with recursively
> defined types that have additional identity constraints.

MITRE has published a severity score of 2.9 LOW (CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L) for this CVE.

## Which versions are affected by GHSA-5w6v-399v-w3cc?

1 open source package ship an affected version, including nokogiri.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `nokogiri` | RubyGems | `pkg:gem/nokogiri` | All versions | 1.18.8 |

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | fixed | `nokogiri` | 1.18.8 |

## How do I fix GHSA-5w6v-399v-w3cc?

Upgrade nokogiri to 1.18.8 or later.

## Is GHSA-5w6v-399v-w3cc being exploited?

There is no known exploitation of GHSA-5w6v-399v-w3cc in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-5w6v-399v-w3cc and fix it if it is affected.

What it is: GHSA-5w6v-399v-w3cc is a vulnerability in nokogiri, published on 21 Apr 2025. 
Exploitation: There is no known exploitation of GHSA-5w6v-399v-w3cc in the wild and no public exploit code.

Affected packages and fixed versions:
- nokogiri (RubyGems): affected all versions; fixed in 1.18.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-5w6v-399v-w3cc/ (Markdown: https://insights.sbomify.com/GHSA-5w6v-399v-w3cc/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-5w6v-399v-w3cc

---
From sbomify Insights: https://insights.sbomify.com/GHSA-5w6v-399v-w3cc/
Summaries are generated and may contain mistakes; the official description above is the record.
