OESA-2026-4923: krb5 security update
Kerberos is a network authentication protocol. It is designed to provide strong authentication for client/server applications by using secret-key cryptography. Security Fix(es):
The RPCSECGSS authentication routines in lib/rpc/authgssprot.c in MIT Kerberos 5 (aka krb5) 1.4 and later do not free partially decoded buffers on failure, which allows remote attackers to cause a denial of service (memory leak in kadmind) via crafted RPCSECGSS messages.(CVE-2026-112315)
xdrkrb5tldata() in lib/kadm5/kadmrpcxdr.c in MIT Kerberos 5 (aka krb5) does not free partially decoded data on failure, which allows remote authenticated users to cause a denial of service (memory leak in kadmind) via crafted RPC requests that trigger a decode failure.(CVE-2026-112316)
krb5ktkdbgetentry() in lib/kdb/keytab.c in MIT Kerberos 5 (aka krb5) 1.2.8 and later does not free decrypted key material when a post-decryption check fails, which allows remote attackers to cause a denial of service (memory leak in the KDC or kadmind) via requests that repeatedly trigger key decryption failures.(CVE-2026-112317)
The policy RPC stubs in kadmin/server/serverstubs.c in MIT Kerberos 5 (aka krb5) 1.5.3 and later do not reject a NULL policy name decoded by xdrnullstring(), which allows remote authenticated users to cause a denial of service (kadmind crash via NULL pointer dereference) by sending a policy request with an empty policy name that reaches authorization checks or logging code.(CVE-2026-112318)
The GSS-RPC layer in MIT Kerberos 5 (aka krb5) does not enforce size limits on XDR-decoded data, which allows remote authenticated users to cause a denial of service (memory exhaustion or excessive CPU consumption in kadmind) via crafted RPC requests that trigger unbounded memory allocations during XDR decoding.(CVE-2026-112319)
The GSS-RPC transport layer in MIT Kerberos 5 (aka krb5) 1.4 and later does not release the previous authentication context when a client switches from an RPCSECGSS or AUTHGSSAPI flavor to a non-GSS flavor on the same TCP connection. This allows remote attackers to cause a denial of service (memory exhaustion in kadmind) by repeatedly establishing and abandoning GSS authentication contexts.(CVE-2026-112320)
The AUTHGSSAPI handler in lib/rpc/svcauthgssapi.c in MIT Kerberos 5 (aka krb5) does not free decoded arguments on certain error paths, which allows remote attackers to cause a denial of service (memory exhaustion in kadmind) via crafted AUTHGSSAPIINIT requests that trigger authentication failures.(CVE-2026-112321)
cleanclient() in lib/rpc/svcauthgssapi.c in MIT Kerberos 5 (aka krb5) restarts its scan from the head of the client list after each removal, resulting in quadratic CPU cost. Remote attackers can cause a denial of service (CPU consumption in kadmind) by accumulating a large number of AUTHGSSAPI client entries.(CVE-2026-112322)
The AUTHGSSAPI handler in lib/rpc/svcauthgssapi.c in MIT Kerberos 5 (aka krb5) 1.5.2 and later allows remote attackers to cause a denial of service (memory exhaustion in kadmind) by sending repeated failed AUTHGSSAPIINIT requests. Each failed request allocates client state that is only freed after a 15-minute expiration timeout, allowing an attacker to accumulate memory faster than it is reclaimed.(CVE-2026-112323)
decodesequenceof() in lib/krb5/asn.1/asn1encode.c in MIT Kerberos 5 (aka krb5) 1.11 and later grows the decoded element array one entry at a time, which allows remote attackers to cause a denial of service (CPU consumption in the KDC) by sending an unauthenticated AS-REQ or TGS-REQ with a large number of elements in a SEQUENCE OF field over TCP.(CVE-2026-119079)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
openeuler/krb5to a version that resolves this vulnerability.Fixed in 1.21.2-24.oe2403sp3
Event History
Child vulnerabilities
Contains the following vulnerabilities.
Frequently Asked Questions
Which services can be disrupted by these flaws?
The reported memory leaks can affect kadmind. One issue can also leak memory in the KDC or kadmind when requests repeatedly trigger key decryption failures.
Does exploitation require authentication?
Not for every issue. Crafted RPCSEC_GSS messages can be sent by remote attackers without stated authentication requirements, while the malformed RPC request issue specifically requires a remote authenticated user.
What is the likely impact of successful exploitation?
The documented impact is denial of service through memory leaks. An attacker can repeatedly send crafted requests or messages that cause decoding or key-decryption failures, consuming memory in the affected service.