# CVE-2024-34394: libxmljs2 namespaces type confusion RCE

> A type confusion vulnerability in libxmljs2 allows attackers to achieve remote code execution or denial of service via crafted XML input.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2024
- **Updated:** 3 Oct 2026
- **Also known as:** GHSA-78h3-pg4x-j8cv

## What is CVE-2024-34394?

CVE-2024-34394 is a high-severity memory corruption vulnerability in libxmljs2, published on 2 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

libxmljs2 is vulnerable to a type confusion vulnerability when parsing a specially crafted XML while invoking the namespaces() function (which invokes XmlNode::get_local_namespaces()) on a grand-child of a node that refers to an entity. This vulnerability can lead to denial of service and remote code execution.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

## Which versions are affected by CVE-2024-34394?

2 open source packages ship an affected version, including libxmljs2.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libxmljs2` | npm | All versions to 0.35.0 | None |
| `libxmljs2` | npm | All versions to 0.35.0 | None |

## How do I fix CVE-2024-34394?

No fix has been published for CVE-2024-34394 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-34394 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34394 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-34394 and fix it if it is affected.

What it is: CVE-2024-34394 is a high-severity memory corruption vulnerability in libxmljs2, published on 2 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-34394 exists.

Affected packages and fixed versions:
- libxmljs2 (npm): affected all versions up to 0.35.0; no fix listed
- libxmljs2 (npm): affected all versions up to 0.35.0; no fix listed

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/CVE-2024-34394/ (Markdown: https://insights.sbomify.com/CVE-2024-34394/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-34394
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-34394
- OSV: https://osv.dev/vulnerability/CVE-2024-34394

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-34394/
Summaries are generated and may contain mistakes; the official description above is the record.