# CVE-2026-131845: Poppler 21.01.0 through 26.11.0 TOCTOU Race Condition in signDocument()


- **Severity:** Medium 4.1 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:N/VI:H/VA:N/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-2hv3-q4rm-q68w, UBUNTU-CVE-2026-131845

## What is CVE-2026-131845?

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

### Official description

Poppler 21.01.0 through 26.11.0 contains a time-of-check time-of-use race condition in FormWidgetSignature::signDocument() that allows local attackers to obtain valid signatures over altered content. Attackers with write access to the output file or directory can overwrite or swap the PDF between writing and hashing, causing the signer's key to sign attacker-controlled content.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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


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

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

## Is CVE-2026-131845 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-131845 is a medium-severity vulnerability in freedesktop poppler, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-131845 in the wild and no public exploit code.

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

## Sources

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

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