CVE-2025-59088: Python-kdcproxy: unauthenticated ssrf via realm‑controlled dns srv

Published Sep 8, 2025
·
Updated

An unauthenticated client can control which host:port the proxy connects to by choosing a realm whose DNS publishes SRV records, leading to unbounded SRV auto discovery being used to make server-side connections across a trust boundary (including localhost/RFC1918) with no port/address policy and no validation of upstream responses, resulting in SSRF (CWE-918), data exfiltration, and origin-cloaked egress.

Other sources

If kdcproxy receives a request for a realm which does not have server addresses defined in its configuration, by default, it will query SRV records in the DNS zone matching the requested realm name. This creates a server-side request forgery vulnerability, since an attacker could send a request for a realm matching a DNS zone where they created SRV records pointing to arbitrary ports and hostnames (which may resolve to loopback or internal IP addresses). This vulnerability can be exploited to probe internal network topology and firewall rules, perform port scanning, and exfiltrate data. Deployments where the "usedns" setting is explicitly set to false are not affected.

MITRE

Affected Software

1 affected component
pypi/python-kdcproxy

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Ensure the kdcproxy configuration has "use_dns" set to false to prevent default SRV record DNS auto-discovery for attacker-supplied realms.

    kdcproxy (Python-kdcproxy) use_dns = false
  2. Compensating control

    If SRV-based discovery is required, restrict DNS SRV records and the set of realms that kdcproxy is allowed to query so attackers cannot create/choose realms with SRV records that resolve to localhost (127.0.0.1) or RFC1918/internal addresses/ports.

Event History

Sep 8, 2025
Data Sourced
via Red Hat·09:33 PM
DescriptionSeverityAffected Software
Nov 12, 2025
CVE Published
via MITRE·04:35 PM
Data Sourced
via MITRE·04:35 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-59088?

CVE-2025-59088 is classified as a high-severity vulnerability due to its potential for server-side request forgery.

2

How do I fix CVE-2025-59088?

To mitigate CVE-2025-59088, configure valid server addresses for all realms in the kdcproxy configuration.

3

What software is affected by CVE-2025-59088?

CVE-2025-59088 affects the Python kdcproxy software.

4

Can CVE-2025-59088 lead to unauthorized access?

Yes, CVE-2025-59088 can potentially lead to unauthorized access via server-side request forgery.

5

Is there a workaround for CVE-2025-59088?

A temporary workaround for CVE-2025-59088 is to disable the DNS query feature for realms without defined server addresses.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203