CVE-2026-112318 · Infrastructure
NO FIX YET
The kadmin policy RPC stubs in MIT Kerberos 5 1.5.3 and later do not reject a NULL policy name, so a crafted request dereferences a null pointer. An authenticated remote user can crash 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.
Organisations running MIT Kerberos kadmind, the administration server for a Kerberos realm, from version 1.5.3 onward. Only the kadmind service is exposed; hosts running only the KDC or clients are not described as affected. Sites that do not expose kadmin remotely are less exposed, but the sources do not say more.
Not affected if auth-required
Who cares kadmind, kerberos, mit-kerberos, self-hosted
Unknown from the sources.
No fix yet, per the sources.
The policy RPC stubs in kadmin/server/server_stubs.c in MIT Kerberos 5 (aka krb5) 1.5.3 and later do not reject a NULL policy name decoded by xdr_nullstring(), 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.
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.