Quick answers
- Is CVE-2026-112322 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112322 being exploited in the wild.
- How severe is CVE-2026-112322?
- High severity, with a CVSS score of 7.5, published 9 November 2026.
- Which products and versions are affected?
- MIT Kerberos 5.
- Is there a fix for CVE-2026-112322?
- No fixed version is recorded yet. Restrict network access to kadmind to trusted hosts, or disable it in favor of the kadmin.local server-side command-line tool for administration operations if possible. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-112322 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-112322?
- Check whether you run Mit Kerberos 5. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
Restrict network access to kadmind to trusted hosts, or disable it in favor of the kadmin.local server-side command-line tool for administration operations if possible.
Technical details
The clean_client() function in lib/rpc/svc_auth_gssapi.c has an algorithmic inefficiency that restarts scanning the client list from the beginning after each entry removal, resulting in quadratic time complexity. A remote attacker without authentication can accumulate AUTH_GSSAPI client entries to trigger excessive CPU consumption in kadmind, achieving denial of service.
Affected products
- MIT Kerberos 5
Timeline
- 2026-11-09: disclosed