# CVE-2026-114629: Web::Simple versions before 0.035 for Perl allocate a buffer sized by the Content-Length header for urlencoded body parameters.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 24 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-114629, GHSA-38cx-9rf2-hq5v

## What is CVE-2026-114629?

CVE-2026-114629 is a vulnerability, published on 24 Oct 2026. 

### Official description

Web::Simple versions before 0.035 for Perl allocate a buffer sized by the Content-Length header for urlencoded body parameters.

Web::Dispatch::ParamParser::get_unpacked_body_from reads an application/x-www-form-urlencoded body using a single read call, with no cap and the return value ignored. Perl's read grows the buffer to the requested length before reading, so the declared Content-Length determines the allocation.

An attacker can trigger this through any route whose dispatch specification has a % body-parameter match, such as sub (POST + %name=), sending a Content-Length far larger than the body actually sent. No authentication is involved.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

## Which versions are affected by CVE-2026-114629?


## How do I fix CVE-2026-114629?

Upgrade to a fixed version.

## Is CVE-2026-114629 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114629 and fix it if it is affected.

What it is: CVE-2026-114629 is a vulnerability, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114629 in the wild and no public exploit code.

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

## Sources

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

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