Quick answers
- Is CVE-2026-112320 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112320 being exploited in the wild.
- How severe is CVE-2026-112320?
- High severity, with a CVSS score of 7.5, published 9 November 2026.
- Which products and versions are affected?
- Mit Kerberos 5 1.4 and later.
- Is there a fix for CVE-2026-112320?
- No fixed version is recorded yet. Restrict network access to kadmind to trusted hosts, or disable it in favor of 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-112320 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-112320?
- Check whether you run Mit Kerberos 5 at an affected version. 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 kadmin.local server-side command-line tool for administration operations if possible.
Technical details
The GSS-RPC transport layer in MIT Kerberos 5 versions 1.4 and later does not properly release authentication context when a client switches from RPCSEC_GSS or AUTH_GSSAPI to a non-GSS flavor on the same TCP connection. An unauthenticated remote attacker with network access to kadmind can repeatedly establish and abandon GSS authentication contexts to trigger unbounded heap memory exhaustion, causing denial of service. No fix has been publicly released at the time of publication.
Affected products
- MIT Kerberos 5 1.4 and later
Timeline
- 2026-11-09: disclosed