Skip to main content
VulnerabilityPublished

CVE-2026-116497: A NULL pointer dereference vulnerability was found in gssproxy

Source GCVE Database

0
Authoritative record:CVE-2026-116497· Medium 5.5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 16:38 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat Enterprise Linux 10gssproxyAffected–Fixed in–
Red Hat Enterprise Linux 7gssproxyAffected–Fixed in–
Red Hat Enterprise Linux 8gssproxyAffected–Fixed in–
Red Hat Enterprise Linux 9gssproxyAffected–Fixed in–
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Affected–Fixed in–
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Affected–Fixed in–

AI-suggested

There is no complete mitigation without applying a code fix. As a partial workaround, administrators can configure the gssproxy systemd unit with "Restart=on-failure" to enable automatic restarts after a crash, reducing downtime. However, this does not prevent crashes and a persistent attacker can still cause repeated denial of service. Monitoring and manual restarts remain necessary until a patch is applied.

Description

A NULL pointer dereference vulnerability in gssproxy allows any local user to crash the daemon by sending a GSSX_INIT_SEC_CONTEXT request missing the target_name field. This causes the daemon to crash and not restart automatically, resulting in a persistent denial of service that affects dependent services such as Kerberized NFS and IdM.

References

Community reviews

Loading reviews…