CVSS 3.1
5.5 mediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HMedium (5.5). EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExplain CVE-2026-116497 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116497?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116497?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-116497 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | gssproxy | no fix listed | DEBIAN-CVE-2026-116497 |
| Ubuntu | 18.04:LTS, 20.04:LTS, 22.04:LTS and 3 more | gssproxy | no fix listed | UBUNTU-CVE-2026-116497 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.
Red Hat rates this Moderate.
Red Hat has confirmed this vulnerability in gssproxy as shipped in Red Hat Enterprise Linux. The gssproxy daemon crashes when it receives a GSSX_INIT_SEC_CONTEXT request with the target_name field absent, due to a missing NULL pointer check. This can be triggered by any local user without authentication, causing a denial of service that persists until the daemon is manually restarted. Services that depend on gssproxy for Kerberos credential management, including NFS and IdM, are affected while the daemon is down.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | gssproxy | Fix deferred | |
| Red Hat Enterprise Linux 7 | gssproxy | Fix deferred | |
| Red Hat Enterprise Linux 8 | gssproxy | Fix deferred | |
| Red Hat Enterprise Linux 9 | gssproxy | Fix deferred | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Fix deferred | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Fix deferred | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-116497.