Skip to content
VulniPulse
Advisory severityHigh7.3Red Hat Linux

High [CVE-2026-112177] Reintroduction of.charkeys -dSAFER bypass in RHEL 8

This high-severity Red Hat Linux advisory covers CVE-2026-112177; related products: Red Hat Enterprise Linux 8, Red Hat package: ghostscript.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-112177 Source published Source updated

VulniPulse record published Record updated

CVE-2026-112177
Related products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open source advisory

Get an email when Red Hat Linux RHEL & SELinux publishes the next one.

See Red Hat Linux RHEL & SELinux's last 90 days of advisories first. Then choose the free weekly digest, or a free month of real-time alerts with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat Linux RHEL & SELinux

Summary

Reintroduction of.charkeys -dSAFER bypass in RHEL 8. Red Hat rates this important (CVSS 7.3).

Weakness: CWE-648.

Affected products named by the advisory: Red Hat Enterprise Linux 8; Red Hat package: ghostscript.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.

Official advisory · high-confidence parse· fetched 11 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists. Confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 11 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to eliminate privileged .forceput operations in the .charkeys procedure to enforce -dSAFER sandbox boundaries: upgrade to the fixed Ghostscript builds, which replace .forceput invocations with standard put operations in the /.charkeys procedure in Resource/Init/gs_ttf.ps, closing all 2 injection vectors (crafted PostScript document, malicious TrueType font processing). Until patched, this is a concern on Ghostscript on Linux (RHEL 8) processing untrusted input, such as print or document-conversion services, so Restrict or halt processing of untrusted PostScript documents and TrueType font inputs across document-conversion and printing services that invoke Ghostscript. As a compensating measure, Use auditd to log unauthorized file access attempts and unexpected execve syscalls spawned by the Ghostscript process, Run SELinux in enforcing mode to confine the Ghostscript process to a restricted domain, Use Linux mount and PID namespaces to restrict filesystem and process visibility for Ghostscript execution, Deploy an EDR agent to detect and terminate unexpected shell or child process spawns from Ghostscript, and Use Falco or eBPF runtime security to detect anomalous child process execution and unauthorized file reads. These controls limit blast radius and contain exploitation, but they do not fix the underlying privileged .forceput sandbox bypass — apply the upstream patch to fully remediate. Highest-impact CME: CME-1002 Audit Subsystem (auditd) (medium)

Official advisory · high-confidence parse· fetched 11 days ago·verify at source

All Red Hat Linux advisories

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.