# CVE-2026-125396: Ghostscript before 10.08.0 -dSAFER Bypass via .putgstringcopy .forceput Recovery


- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-125396, GHSA-hg3g-c775-3fpj, UBUNTU-CVE-2026-125396

## What is CVE-2026-125396?

CVE-2026-125396 is a high-severity vulnerability in ArtifexSoftware ghostpdl, published on 9 Nov 2026. 

### Official description

Ghostscript before 10.08.0 contains a -dSAFER bypass vulnerability in the .putgstringcopy procedure in gs_fonts.ps, which calls the privileged .forceput operator without checking operand types. Attackers can supply crafted PostScript or PDF documents that trigger a type error, recover .forceput via a custom error handler, and cause a use-after-free across save/restore to execute arbitrary code.

Weakness: CWE-648 (Incorrect Use of Privileged APIs)

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


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

Upgrade to a fixed version.

## Is CVE-2026-125396 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125396 is a high-severity vulnerability in ArtifexSoftware ghostpdl, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125396 in the wild and no public exploit code.

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

## Sources

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

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