A critical Server-Side Request Forgery (SSRF) vulnerability, tracked as CVE-2025-59775, was identified in Apache HTTP Server running on Windows systems. The flaw occurs when the server is configured with AllowEncodedSlashes On and MergeSlashes Off, allowing attackers to exploit SSRF to leak NTLM hashes to malicious servers. This vulnerability poses a significant risk as it can be exploited remotely without authentication or user interaction, potentially exposing sensitive credentials.
Apache has released version 2.4.66 to address this issue, and users are strongly advised to upgrade to mitigate the risk. The vulnerability is rated as high severity with a CVSS score of 7.5, and its exploitation could lead to the compromise of Windows authentication credentials. The update also addresses a suexec bypass, further enhancing the security posture of affected systems.

See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
CVE-2025-59775 was publicly documented as a server-side request forgery vulnerability in Apache HTTP Server on Windows. Public CVE listing made the issue and its classification visible to defenders and researchers.
Apache released HTTP Server version 2.4.66 to fix CVE-2025-59775, an SSRF vulnerability affecting Windows deployments that could expose NTLM hashes. The release also addressed a suexec bypass issue.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
cvedetails.com
Open sourcesecurityonline.info
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.