Skip to main content
Mallory
UnratedVulnerability

CVE-2026-111423: PAC Authorization Bypass in MIT Kerberos

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

CVE-2026-111423 is a PAC server-checksum verification logic error affecting MIT krb5 releases starting with 1.21, before the applicable security fix. Server applications incorrectly treat a ticket's Privilege Attribute Certificate (PAC) as verified even when its server checksum is invalid. An authenticated attacker can exploit this behavior using a forged PAC to bypass an application server's PAC-based authorization checks. MIT Kerberos 5 version 1.22.3 corrects the checksum verification logic and closes a KDC authorization-data filtering loophole that permits client-supplied forged PAC values in service tickets.

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 authenticated attacker can cause an affected application server to trust forged PAC authorization data, potentially obtaining access or privileges not granted to the authenticated principal. The resulting access depends on how the application uses PAC attributes for authorization.

Remediation

Patch, then assume compromise.

Upgrade either the KDC or the affected application server to MIT Kerberos 5 version 1.22.3 or later, or install the corresponding vendor-backported security update. Updating either component prevents this forged-PAC authorization bypass. For Alpine Linux, the security update is available in krb5 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-111423 exploited in the wild?
As of Nov 21, 2026, Mallory has no reports of CVE-2026-111423 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-111423?
As of Nov 21, 2026, Mallory has found no public exploit for CVE-2026-111423.
Is there a patch for CVE-2026-111423?
Upgrade either the KDC or the affected application server to MIT Kerberos 5 version 1.22.3 or later, or install the corresponding vendor-backported security update. Updating either component prevents this forged-PAC authorization bypass.
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.