# CVE-2026-112177: Ghostscript: reintroduction of .charkeys -dsafer bypass in rhel 8


- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-4hx3-pq6p-jhg6

## What is CVE-2026-112177?

CVE-2026-112177 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 20 Oct 2026. 

### Official description

A flaw was found in Ghostscript as shipped with Red Hat Enterprise Linux 8. The correction for CVE-2019-14869 was omitted during the rebase from version 9.25 to 9.27, leaving privileged .forceput operations in the .charkeys procedure insufficiently protected. Processing a specially crafted PostScript file may allow an attacker to bypass -dSAFER restrictions and access files outside the permitted paths or execute commands with the permissions of the Ghostscript process.

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

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


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

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

## Is CVE-2026-112177 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112177 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112177 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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-112177/ (Markdown: https://insights.sbomify.com/CVE-2026-112177/index.md)
```

## Sources

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

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