Skip to main content
Mallory
UnratedVulnerability

CVE-2026-71199: Authentication Indicator Bypass in MIT krb5 CAMMAC Validation

Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days25 mentions · peak 6 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-71199CWE-354

CVE-2026-71199 is an authentication-policy bypass vulnerability in MIT krb5's handling of authentication indicators within CAMMAC authorization-data containers. The affected functionality was introduced in release 1.14. An authenticated attacker can use an unkeyed checksum in a CAMMAC container to alter authentication indicators and bypass requirements enforced using those indicators. Unpatched deployments can consequently accept authentication assertions that do not satisfy the intended security policy.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation undermines authentication-indicator integrity and can permit access to services or protected information without satisfying the required authentication policy. The vulnerability's CVSS v2 assessment indicates complete confidentiality and integrity impacts, with no availability impact.

Mitigation

If you can’t patch tonight, do this now.

No temporary workaround is specified. Prioritize patching KDCs that enforce authentication indicator requirements.

Remediation

Patch, then assume compromise.

Install vendor-patched krb5 packages for the applicable operating system and support stream. Fixed Red Hat package releases include 1.21.1-10.el9_9.2 for RHEL 9, 1.21.1-10.el9_8.3 for RHEL 9.8 support streams, 1.21.3-11.el10_3.2 for RHEL 10, and 1.21.3-10.el10_2.2 for RHEL 10.2 support streams. For upstream installations, upgrade to Kerberos 1.22.3 or later in accordance with MITKRB5-SA-2026-001. Distribution packages may contain backported fixes despite retaining an older upstream version.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-71199 exploited in the wild?
As of Nov 21, 2026, Mallory has no reports of CVE-2026-71199 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-71199?
As of Nov 21, 2026, Mallory has found no public exploit for CVE-2026-71199.
Is there a patch for CVE-2026-71199?
Install vendor-patched krb5 packages for the applicable operating system and support stream. Fixed Red Hat package releases include 1.21.1-10.el9_9.2 for RHEL 9, 1.21.1-10.el9_8.3 for RHEL 9.8 support streams, 1.21.3-11.el10_3.2 for RHEL 10, and 1.21.3-10.el10_2.2 for RHEL 10.2 support streams.
Activity feed

Recent activity

25 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+17 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.