# CVE-2026-131844: Poppler through 26.11.0 Uncontrolled Memory Allocation via Forged HTTP Content-Length


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-fc2f-j8qq-68fj, UBUNTU-CVE-2026-131844

## What is CVE-2026-131844?

CVE-2026-131844 is a high-severity vulnerability in freedesktop poppler, published on 17 Nov 2026. 

### Official description

Poppler through 26.11.0 contains an uncontrolled memory allocation vulnerability in the libcurl-based remote file loader that trusts unvalidated HEAD Content-Length values in CurlCachedFileLoader::init(). Malicious HTTP servers can return an enormous Content-Length so CachedFile resizes its chunk cache accordingly, aborting pdfinfo or PDFDocFactory-based applications with std::bad_alloc for denial of service.

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

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


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

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

## Is CVE-2026-131844 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-131844 is a high-severity vulnerability in freedesktop poppler, published on 17 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-131844 exists.

Affected product: freedesktop poppler. 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-2026-131844/ (Markdown: https://insights.sbomify.com/CVE-2026-131844/index.md)
```

## Sources

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

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