CVE
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.
Written by a model from the sources below. Verify against them.
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
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Poppler opens remote http(s) PDFs through its libcurl-based remote file loader.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 24/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Original 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.
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.
“Poppler through 26.11.0”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Poppler opens remote http(s) PDFs through its libcurl-based remote file loader.Workaround: 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.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- CVE published1 day
- First seen by cve.now
Affected versions
- freedesktop poppler
through 26.11.0
Evidence 6
Vendor advisory · 2
Establishes: Affected and fixed versions.
- Link
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Write-ups · 1
Establishes: Technical detail and context.
- Report
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-131844
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: cve.now feed data
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: vulncheck.com, gitlab.freedesktop.org
Which versions are affected by CVE-2026-131844?
poppler: through 26.11.0.Source: cve.now feed data
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: vulncheck.com, gitlab.freedesktop.org
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: vulncheck.com, gitlab.freedesktop.org
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: vulncheck.com, gitlab.freedesktop.org