Vulnerability DatabaseCVE-2026-119079

CVE-2026-119079: 
Kerberos vulnerability analysis and mitigation

Overview

CVE-2026-119079 is a denial-of-service vulnerability in MIT Kerberos 5 (krb5) caused by an algorithmic complexity flaw in the decode_sequence_of() function within lib/krb5/asn.1/asn1_encode.c. Affecting krb5 version 1.11 and later, the function grows its decoded element array one entry at a time, resulting in quadratic time complexity when processing SEQUENCE OF fields with a large number of elements. An unauthenticated remote attacker can exploit this by sending crafted AS-REQ or TGS-REQ messages over TCP to cause excessive CPU consumption in the KDC. The vulnerability was reported on November 9, 2026, and carries a CVSS v3.1 base score of 7.5 (High) (Red Hat CVE, Red Hat Bugzilla).

Technical details

The root cause is classified as CWE-408 (Incorrect Behavior Order: Early Amplification). In decode_sequence_of(), the destination buffer is reallocated with realloc() on every single loop iteration — growing by exactly one element each time — rather than using geometric (doubling) growth. This means decoding a SEQUENCE OF field with N elements triggers O(N²) total memory operations. The vulnerable code path is reachable before authentication: krb5kdc decodes incoming AS-REQ and TGS-REQ messages via decode_krb5_as_req() and decode_krb5_tgs_req() in src/kdc/dispatch.c before any credential validation occurs. A practical trigger is the PrincipalName.name-string field, defined as a counted SEQUENCE OF GeneralString, allowing an attacker to pack a near-maximum-size TCP payload (~1,048,572 bytes) with a very large number of short string elements. The proposed fix replaces per-element reallocation with geometric capacity doubling (Red Hat Bugzilla, Red Hat CVE).

Impact

Successful exploitation causes excessive CPU consumption in the krb5kdc daemon, degrading or disabling Kerberos authentication services for all users and systems relying on the affected KDC. Because the KDC is a central authentication authority in enterprise environments, its unavailability can prevent logins, service ticket issuance, and access to Kerberos-protected resources across the entire domain. There is no confidentiality or integrity impact — the vulnerability is strictly an availability issue with no code execution or data disclosure potential (Red Hat CVE, Red Hat Bugzilla).

Exploitability

A proof-of-concept reproduction procedure is documented in the Red Hat Bugzilla entry, describing how to craft and send oversized AS-REQ or TGS-REQ messages with large PrincipalName.name-string SEQUENCE OF fields; no runnable exploit code or crafted payload bytes are publicly available (Red Hat Bugzilla). The vulnerability is automatable (no authentication, no user interaction required) and network-reachable, making it straightforward to exploit at scale. There is no evidence of in-the-wild exploitation as of the time of disclosure. The EPSS score is approximately 0.638%, and the vulnerability is not listed in the CISA KEV catalog. Microsoft also published an advisory for this CVE on November 13, 2026 (Microsoft).

Exploitation steps

  1. Reconnaissance: Identify internet-facing or network-accessible krb5kdc instances listening on TCP port 88 using network scanners (e.g., Nmap, Shodan). Confirm the target is running MIT krb5 version 1.11 or later.
  2. Craft malicious Kerberos request: Construct a syntactically valid AS-REQ or TGS-REQ message where the PrincipalName.name-string field contains a very large number of short GeneralString elements encoded as a SEQUENCE OF GeneralString. Keep the overall request size just below the TCP payload cap of approximately 1,048,572 bytes to maximize the number of elements.
  3. Send requests over TCP: Transmit the crafted request(s) repeatedly over TCP to port 88 of the target KDC. UDP is not the primary attack vector for this issue; TCP is required to send near-cap-sized payloads.
  4. Trigger quadratic decode: Each received request causes decode_sequence_of() to perform one realloc() per element in the sequence, resulting in O(N²) CPU work before any authentication check occurs.
  5. Observe impact: Monitor the target KDC for elevated CPU utilization and degraded response times for legitimate Kerberos clients, confirming successful denial-of-service (Red Hat Bugzilla).

Indicators of compromise

  • Network: Repeated large TCP connections (near 1 MB payload) to port 88/TCP from one or more source IPs; unusually high volume of AS-REQ or TGS-REQ messages over TCP from untrusted or external sources.
  • Process: Sustained high CPU utilization by the krb5kdc process without a corresponding increase in legitimate authentication traffic; krb5kdc becoming unresponsive or slow to process legitimate requests.
  • Logs: KDC logs showing a high rate of incoming TCP requests, particularly from a single or small set of source addresses; log entries indicating repeated pre-authentication decode activity without successful authentication completions.
  • System: Elevated system load average on the KDC host correlating with spikes in inbound Kerberos TCP traffic (Red Hat Bugzilla, Red Hat CVE).

Mitigation and workarounds

Red Hat has released patched packages addressing this vulnerability: krb5-1.21.3-11.el10_3.2 for RHEL 10 (RHSA-2026:99624), krb5-1.21.3-10.el10_2.2 for RHEL 10.2 EUS (RHSA-2026:99625), krb5-1.21.1-10.el9_9.2 for RHEL 9 (RHSA-2026:99715), krb5-1.21.1-10.el9_8.3 for RHEL 9.8 EUS (RHSA-2026:99716), and krb5-1.22.3-0.1.hum1 for Red Hat Hardened Images (RHSA-2026:97811) (Red Hat RHSA-99624, Red Hat RHSA-97811). As a network-level workaround, restrict TCP port 88 access to trusted internal networks using firewall rules (e.g., firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="192.168.1.0/24" port port="88" protocol="tcp" accept') and remove broad public access to port 88/TCP. Additionally, consider implementing rate limiting for large Kerberos TCP requests from untrusted sources (Red Hat CVE).

Community reactions

Red Hat classified this vulnerability as Important severity, noting that remote unauthenticated attackers can cause excessive CPU consumption and degrade KDC availability without valid credentials or user interaction, and specifically highlighted risk to krb5kdc daemons exposed to untrusted TCP networks (Red Hat CVE). The vulnerability was discovered and reported by AISLE Research in partnership with Red Hat. Community discussion appeared on oss-security mailing lists and social media (Mastodon/RedPacketSecurity), and the issue was picked up by security tracking platforms including VulDB, Tenable (Nessus plugin 377847), and ZeroPath, which published a dedicated technical blog post (ZeroPath Blog).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Fixed

bookworm

krb5

Affected

sid

krb5: 1.22.3-1

Fixed

trixie

krb5

Affected

Ubuntu

Unknown

bionic (esm-infra)

krb5

Unknown

devel

krb5

Unknown

focal (esm-infra)

krb5

Unknown

jammy

krb5

Unknown

noble

krb5

Unknown

resolute

krb5

Unknown

trusty (esm-infra-legacy)

krb5

Unknown

xenial (esm-infra-legacy)

krb5

Unknown

RHEL / CentOS

Fixed

RHEL 8

krb5.src

Affected

RHEL 9

:appstream:krb5-0:1.21.1-10.el9_8.3.src

Fixed

RHEL 10

krb5-0:1.21.3-10.el10_2.2.src

Fixed

Alpine

Fixed

edge

krb5: 1.22.3-r0

Fixed

v3.23

krb5: 1.22.3-r0

Fixed

Source: This report was generated using AI

Related Kerberos vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-71199HIGH8.1
  • Kerberos logoKerberos
  • krb5-server-debuginfo
NoYesNov 13, 2026
CVE-2026-71200HIGH7.5
  • Kerberos logoKerberos
  • krb5-server-debuginfo
NoYesNov 13, 2026
CVE-2026-118380HIGH7.4
  • Kerberos logoKerberos
  • krb5-libs
NoYesNov 13, 2026
CVE-2026-107884MEDIUM6.7
  • Kerberos logoKerberos
  • krb5
NoYesNov 13, 2026
CVE-2026-111423MEDIUM4.2
  • Kerberos logoKerberos
  • seal-krb5
NoYesNov 13, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management