CVE-2025-59089: Allocation of Resources Without Limits or Throttling in latchset kdcproxy
If an attacker causes kdcproxy to connect to an attacker-controlled KDC server (e.g. through server-side request forgery), they can exploit the fact that kdcproxy does not enforce bounds on TCP response length to conduct a denial-of-service attack. While receiving the KDC's response, kdcproxy copies the entire buffered stream into a new buffer on each recv() call, even when the transfer is incomplete, causing excessive memory allocation and CPU usage. Additionally, kdcproxy accepts incoming response chunks as long as the received data length is not exactly equal to the length indicated in the response header, even when individual chunks or the total buffer exceed the maximum length of a Kerberos message. This allows an attacker to send unbounded data until the connection timeout is reached (approximately 12 seconds), exhausting server memory or CPU resources. Multiple concurrent requests can cause accept queue overflow, denying service to legitimate clients.
AI Analysis
Technical Summary
The vulnerability in latchset kdcproxy (CVE-2025-59089) involves the lack of bounds enforcement on TCP response lengths from KDC servers. During response reception, kdcproxy copies the entire buffered stream into new buffers on each recv() call, even if the transfer is incomplete, causing excessive memory and CPU consumption. Additionally, it accepts incoming response chunks as long as the received length does not exactly match the response header length, allowing attackers to send unbounded data until connection timeout (~12 seconds). Multiple concurrent exploit attempts can overflow the accept queue, resulting in denial-of-service to legitimate clients. This vulnerability has a CVSS 3.1 base score of 5.9 (medium severity) and does not impact confidentiality or integrity but affects availability. Red Hat has issued an official security advisory and patch for python-kdcproxy in Red Hat Enterprise Linux 9.6, 9.8, and related Extended Update Support and Extended Life Cycle versions.
Potential Impact
Successful exploitation results in denial-of-service by exhausting server memory and CPU resources due to unbounded TCP upstream buffering in kdcproxy. This can also cause accept queue overflow, preventing legitimate client connections. There is no impact on confidentiality or integrity.
Mitigation Recommendations
An official fix is available from Red Hat. Users should apply the python-kdcproxy security update provided in Red Hat Enterprise Linux 9.6, 9.8, and Extended Update Support and Extended Life Cycle releases. Refer to Red Hat advisory RHSA-2025:21138 and RHSA-2025:21139 and the update instructions at https://access.redhat.com/articles/11258. No additional mitigation is required once the patch is applied.
CVE-2025-59089: Allocation of Resources Without Limits or Throttling in latchset kdcproxy
Description
If an attacker causes kdcproxy to connect to an attacker-controlled KDC server (e.g. through server-side request forgery), they can exploit the fact that kdcproxy does not enforce bounds on TCP response length to conduct a denial-of-service attack. While receiving the KDC's response, kdcproxy copies the entire buffered stream into a new buffer on each recv() call, even when the transfer is incomplete, causing excessive memory allocation and CPU usage. Additionally, kdcproxy accepts incoming response chunks as long as the received data length is not exactly equal to the length indicated in the response header, even when individual chunks or the total buffer exceed the maximum length of a Kerberos message. This allows an attacker to send unbounded data until the connection timeout is reached (approximately 12 seconds), exhausting server memory or CPU resources. Multiple concurrent requests can cause accept queue overflow, denying service to legitimate clients.
CVSS v3.1
Score 5.9medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in latchset kdcproxy (CVE-2025-59089) involves the lack of bounds enforcement on TCP response lengths from KDC servers. During response reception, kdcproxy copies the entire buffered stream into new buffers on each recv() call, even if the transfer is incomplete, causing excessive memory and CPU consumption. Additionally, it accepts incoming response chunks as long as the received length does not exactly match the response header length, allowing attackers to send unbounded data until connection timeout (~12 seconds). Multiple concurrent exploit attempts can overflow the accept queue, resulting in denial-of-service to legitimate clients. This vulnerability has a CVSS 3.1 base score of 5.9 (medium severity) and does not impact confidentiality or integrity but affects availability. Red Hat has issued an official security advisory and patch for python-kdcproxy in Red Hat Enterprise Linux 9.6, 9.8, and related Extended Update Support and Extended Life Cycle versions.
Potential Impact
Successful exploitation results in denial-of-service by exhausting server memory and CPU resources due to unbounded TCP upstream buffering in kdcproxy. This can also cause accept queue overflow, preventing legitimate client connections. There is no impact on confidentiality or integrity.
Mitigation Recommendations
An official fix is available from Red Hat. Users should apply the python-kdcproxy security update provided in Red Hat Enterprise Linux 9.6, 9.8, and Extended Update Support and Extended Life Cycle releases. Refer to Red Hat advisory RHSA-2025:21138 and RHSA-2025:21139 and the update instructions at https://access.redhat.com/articles/11258. No additional mitigation is required once the patch is applied.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- redhat
- Date Reserved
- 2025-09-08T21:43:30.846Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/errata/RHSA-2025:21138","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2025:21139","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2025:21140","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2025:21141","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2025:21142","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2025:21448","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2025:21748","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2025:21806","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2025:21818","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2025:21819","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2025:21820","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2025:21821","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2025:22982","vendor":"Red Hat"},{"url":"https://access.redhat.com/security/cve/CVE-2025-59089","vendor":"Red Hat"}]
Threat ID: 6914bbf8be619665a2474cfb
Added to database: 11/12/2025, 16:55:20 UTC
Last enriched: 07/02/2026, 22:03:40 UTC
Last updated: 09/10/2026, 19:36:51 UTC
Views: 262
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.