CVE-2026-112319 · Infrastructure
NO FIX YET
MIT Kerberos 5 (krb5) GSS-RPC decoding does not limit the size of XDR-decoded data, so an attacker can trigger huge allocations. An authenticated remote user can exhaust memory or CPU in the kadmind administration daemon, causing denial of service.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Organizations running MIT Kerberos kadmind, the krb5 administration server, that accept GSS-RPC requests from authenticated users. Hosts that run only the KDC or client tools are not described by the sources as exposed. unknown beyond this.
Not affected if no-kadmind, unauthenticated-only-clients
Who cares kadmind, kerberos, krb5, linux
Unknown from the sources.
No fix yet, per the sources.
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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.