# CVE-2006-10003: XML::Parser versions through 2.47 for Perl has an off-by-one heap buffer overflow in st_serial_stack

> An off-by-one heap buffer overflow in the Perl XML::Parser library allows attackers to execute arbitrary code or cause denial of service via deeply nested XML.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/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:** Yes
- **Published:** 19 Mar 2026
- **Updated:** 15 Jul 2026
- **Also known as:** AZL-80196, CLSA-2026-1776940444, CLSA-2026-1777396174, DEBIAN-CVE-2006-10003, DSA-6182-1, GHSA-x2wr-f89p-cqwh, UBUNTU-CVE-2006-10003

## What is CVE-2006-10003?

CVE-2006-10003 is a critical memory corruption vulnerability in TODDR XML::Parser, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

XML::Parser versions through 2.47 for Perl has an off-by-one heap buffer overflow in st_serial_stack.

In the case (stackptr == stacksize - 1), the stack will NOT be expanded. Then the new value will be written at location (++stackptr), which equals stacksize and therefore falls just outside the allocated buffer.

The bug can be observed when parsing an XML file with very deep element nesting

Weakness: CWE-193 (Off-by-one Error), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2006-10003?

It affects 1 product.


Products: Toddr Xml\.

## How do I fix CVE-2006-10003?

Apply the vendor's patch.

## Is CVE-2006-10003 being exploited?

There is no known exploitation of CVE-2006-10003 in the wild and no public exploit code.

## Other vulnerabilities in TODDR XML::Parser

- [CVE-2006-10002](https://insights.sbomify.com/CVE-2006-10002/): Memory corruption in XML::Parser (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-10003 and fix it if it is affected.

What it is: CVE-2006-10003 is a critical memory corruption vulnerability in TODDR XML::Parser, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-10003 in the wild and no public exploit code.

Affected product: TODDR XML::Parser. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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