CVE-2025-3576
MediumCVSS 5.9Exploitation Probability (EPSS)
Low risk26th percentile - higher than 26% of all known CVEs
Summary
A vulnerability in the MIT Kerberos implementation allows GSSAPI-protected messages using RC4-HMAC-MD5 to be spoofed due to weaknesses in the MD5 checksum design. If RC4 is preferred over stronger encryption types, an attacker could exploit MD5 collisions to forge message integrity codes.
Risk Assessment
The risk involves potential unauthorized tampering of transmitted messages, which could compromise data integrity in network communications.
Recommendation
It is recommended to disable or restrict the use of RC4-HMAC-MD5 encryption in favor of stronger algorithms like AES, and apply the latest security patches for MIT Kerberos.
Other vulnerabilities in MIT Kerberos
See all- CVE-2024-37370High
In MIT Kerberos 5 before version 1.21.3, an attacker can modify the Extra Count field of a confidential GSS krb5 wrap token, causing the unwrapped token to appear truncated to the application.
- CVE-2024-37371Critical
In MIT Kerberos 5 before version 1.21.3, an attacker can cause invalid memory reads during GSS message token handling by sending message tokens with invalid length fields.
- CVE-2026-40356Medium
In MIT Kerberos 5 (krb5) before 1.22.3, an integer underflow and resultant out-of-bounds read occur if an application calls gss_accept_sec_context() on a system with a NegoEx mechanism registered in /etc/gss/mech. An unauthenticated remote attacker can trigger this, possibly causing the process to terminate in parse_message.
- CVE-2026-40355Medium
In MIT Kerberos 5 (krb5) before version 1.22.3, there is a NULL pointer dereference when an application calls gss_accept_sec_context() on a system with a NegoEx mechanism registered in /etc/gss/mech. An unauthenticated remote attacker can trigger this, causing the process to terminate in parse_nego_message.
Original NVD description (English source)
A vulnerability in the MIT Kerberos implementation allows GSSAPI-protected messages using RC4-HMAC-MD5 to be spoofed due to weaknesses in the MD5 checksum design. If RC4 is preferred over stronger encryption types, an attacker could exploit MD5 collisions to forge message integrity codes. This may lead to unauthorized message tampering.