Skip to main content
Menu
CVEs

CVE

Poppler memory corruption in NSS signature verification backend

CVE-2026-131847EUVD-2026-128333

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

4.8MediumCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported
Published
Last modified
Reference
Last checked
10/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

Poppler from freedesktop has a use-after-free bug in its NSS signature verification backend. A crafted signed PDF can crash applications or pdfsig when several signatures are checked, or cause incorrect certificate validation results. A local attacker needs no login, but a user must take an action to trigger the bug.

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

Original description

Poppler through 26.11.0 contains a use-after-free vulnerability in NSSCryptoSignBackend.cc that allows attackers to trigger reads of freed CMS arena memory during repeated signature verification. Attackers can supply a signed PDF embedding the signer certificate to crash applications or pdfsig runs validating multiple signatures, or cause incorrect certificate validation results.

cve.now Index

10Pcve.now Index 10 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity4.8/10CVSS 4.8
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

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-131847 (Poppler through 26.11.0 Use-After-Free in NSS Signature Verification Backend), 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-131847 (entry last updated 2026-11-17):
Affected:
- freedesktop poppler: through 26.11.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131847 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131847 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/1856
- https://gitlab.freedesktop.org/poppler/poppler/-/blob/poppler-26.11.0/poppler/NSSCryptoSignBackend.cc#L928-L987
- https://www.vulncheck.com/advisories/poppler-through-26.11.0-use-after-free-in-nss-signature-verification-backend
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-131847
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-131847"}.

Timeline

  1. CVE published1 day
  2. First seen by cve.now

Affected versions

  • freedesktop poppler

    through 26.11.0

Evidence 5

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Link

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Write-ups · 1

Establishes: Technical detail and context.

  1. Report

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-131847

Is CVE-2026-131847 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

Which versions are affected by CVE-2026-131847?

poppler: through 26.11.0.Source: cve.now feed data

More CVEs