CVE-2025-49812·Apache vulnerability
In some mod_ssl configurations on Apache HTTP Server versions through to 2.4.63, an HTTP desynchronisation attack allows a man-in-the-middle attacker to hijack an HTTP session via a TLS upgrade. Only configurations using "SSLEngine optional" to enable TLS upgrades are affected. Users are recommended to upgrade to version 2.4.64, which removes support for TLS upgrade.
- Severity
- high
- Software
- Apache
- Fixed in
- 2.4.64
- Published
- 2025-07-10
Affected versions
Until: 2.4.64
Fixed in: 2.4.64
How to fix this CVE
Upgrade Apache HTTP Server to version 2.4.64 or later to eliminate support for TLS upgrade functionality. If you are running Apache with SSLEngine optional configuration, this upgrade is critical to prevent HTTP session hijacking through man-in-the-middle attacks. Alternatively, disable the SSLEngine optional directive in your Apache configuration as an immediate workaround.
sudo dnf upgrade httpdDefensia detects this vulnerability
How to check if you are affected
- Run 'apache2ctl -v' or 'httpd -v' to check your installed Apache version; versions below 2.4.64 are vulnerable
- Check your Apache configuration files (typically /etc/apache2/mods-enabled/ssl.conf or /etc/httpd/conf.d/ssl.conf) for the presence of 'SSLEngine optional' directive; if found, your server is at risk
- Search Apache access and error logs for repeated CONNECT method requests followed by TLS ClientHello messages on non-standard ports, which may indicate exploitation attempts
- After upgrading to 2.4.64, verify the version with 'apache2ctl -v' or 'httpd -v' and restart Apache with 'sudo systemctl restart apache2' or 'sudo systemctl restart httpd' to confirm the fix is active
FAQ
What is CVE-2025-49812?
This vulnerability is an HTTP request smuggling weakness in Apache's mod_ssl module that allows attackers to desynchronize the HTTP protocol during TLS upgrade negotiation, potentially hijacking user sessions. It only affects configurations where SSLEngine is set to optional, enabling protocol upgrades.
Is CVE-2025-49812 being actively exploited?
No, CVE-2025-49812 is not currently listed in the CISA Known Exploited Vulnerabilities catalog, and no public exploits have been disclosed.
What versions of Apache are affected by CVE-2025-49812?
Apache HTTP Server versions up to and including 2.4.63 are vulnerable if configured with SSLEngine optional. Version 2.4.64 and later have removed TLS upgrade support entirely.
How do I check if my server is vulnerable to CVE-2025-49812?
Run 'apache2ctl -v' or 'httpd -v' to confirm your version is 2.4.63 or earlier, then inspect your Apache configuration files for 'SSLEngine optional' directives in your SSL module configuration.
Does Defensia detect CVE-2025-49812?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Apache is installed on a monitored server, CVE-2025-49812 will appear in your dashboard with remediation steps.
Related Apache CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2025-49812. Free for 1 server.
Get started free