Quick answers
- Is CVE-2026-112321 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112321 being exploited in the wild.
- How severe is CVE-2026-112321?
- 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-112321?
- No fixed version is recorded yet. Restrict network access to kadmind to trusted hosts only, or disable kadmind in favor of kadmin.local server-side command line tool for administration 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-112321 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-112321?
- 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 only, or disable kadmind in favor of kadmin.local server-side command line tool for administration if possible.
Technical details
The AUTH_GSSAPI_INIT handler in lib/rpc/svc_auth_gssapi.c does not free decoded arguments on specific error paths (CWE-772), allowing remote unauthenticated attackers to trigger memory leaks. The vulnerability is reachable via network-based RPC authentication requests that fail validation, causing memory exhaustion in kadmind without requiring valid Kerberos credentials.
Affected products
- MIT Kerberos 5
Timeline
- 2026-11-09: disclosed