Skip to main content
CVE-2025-3576VulnerabilityPublished Updated

SUSE · security update for krb5

Affects SUSESource GCVE Database

0

Not known to be exploited : upgrade to 9.8 or 9.6 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

Severity
Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 9.8, 9.6

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade redhat/krb5 to 9.8 or 9.6.

Affected software

ProductAffectedFixed in
Red Hatredhat/krb5pkg:rpm/redhat/krb5Other threatsAffected
  • <9.6
  • <9.8
Fixed in
  • 9.6
  • 9.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released official security updates that address this vulnerability in krb5 for Red Hat Enterprise Linux 9 and its variants. Users should apply these updates promptly following Red Hat's guidance at https://access.redhat.com/articles/11258 to remediate the issue. No additional mitigation steps are indicated beyond applying the official patches.

Description

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.

References

Community reviews

Loading reviews…