CVE-2026-116497
Gssproxy: gssproxy: null pointer dereference in gssx_init_sec_context crashes daemon
- Medium 5.5
Description
A NULL pointer dereference vulnerability was found in gssproxy. When a GSSX_INIT_SEC_CONTEXT request is received with the target_name field absent, the daemon dereferences the resulting NULL pointer and crashes. The request requires no authentication, allowing any local user to crash the gssproxy daemon via its Unix socket. The daemon does not automatically restart, resulting in a persistent denial of service that also affects dependent services such as Kerberized NFS and IdM.
Key facts
- Published
- 26 Oct 2026
- Last changed
- 5 Nov 2026
- Assigned by
- redhat
- EPSS
- 0.139% likely to be exploited in the next 30 days, higher than 3.326% of CVEs (scores for 17 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 5.5CVSS 3.1, Mediumfrom the CNA (redhat)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
What to do
- There is no way to fully mitigate this vulnerability without applying a code fix. The gssproxy Unix socket must be world-accessible for normal operation, and the default configuration accepts connections from any local user. As a partial workaround, administrators can add "Restart=on-failure" to the gssproxy systemd unit to enable automatic restarts after a crash. This does not prevent the crash but limits the denial-of-service window. Note that a persistent attacker can still outpace the restart cycle.CNA workaround statement
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Red Hat | Red Hat Enterprise Linux 10 |
|
| Red Hat | Red Hat Enterprise Linux 7 |
|
| Red Hat | Red Hat Enterprise Linux 8 |
|
| Red Hat | Red Hat Enterprise Linux 9 |
|
| Red Hat | Red Hat OpenShift Container Platform 4 |
|
| Red Hat | Red Hat OpenShift Container Platform 4 |
|
| Red Hat | Red Hat OpenShift Container Platform 5 |
|
Timeline
- 22 Oct 2026 Reported to Red Hat.
- 26 Oct 2026 Made public.
- 26 Oct 2026 Published