Skip to main content
Mallory
UnratedVulnerability

CVE-2026-107884: MIT krb5 Protected Principal Key Reset via kpasswd

Updated 2 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days17 mentions · peak 5 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-107884CWE-862

CVE-2026-107884 is an authorization-check omission in MIT Kerberos 5 password-change request processing in kadmind, introduced in release 1.15. An authenticated client with kadmin administrative privileges can bypass a principal's lockdown_keys attribute by changing its password through the kpasswd protocol instead of the kadmin protocol. The password-change path fails to enforce the restriction, permitting unauthorized replacement of a protected principal's keys. MIT krb5 1.22.3 adds the missing attribute check.

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.

An administrative client can modify protected principal keys despite the lockdown_keys restriction, violating the realm's administrative security policy. Replacing those keys can enable impersonation of the affected principal and invalidate existing credentials or service keytabs, potentially disrupting authentication for that principal.

Mitigation

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

No vulnerability-specific temporary workaround is specified.

Remediation

Patch, then assume compromise.

Upgrade the server running kadmind to MIT krb5 1.22.3 or later, or install the applicable vendor update that backports enforcement of lockdown_keys during password-change protocol requests. 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. Alpine Linux provides the fix in 1.22.3-r0 or later.

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-107884 exploited in the wild?
As of Nov 20, 2026, Mallory has no reports of CVE-2026-107884 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-107884?
As of Nov 20, 2026, Mallory has found no public exploit for CVE-2026-107884.
Is there a patch for CVE-2026-107884?
Upgrade the server running kadmind to MIT krb5 1.22.3 or later, or install the applicable vendor update that backports enforcement of lockdown_keys during password-change protocol requests. 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.
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 activity2Community discussion across Reddit, Mastodon, and other social sources.