Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
3.7

CVE-2026-61813: ModSecurity may accept wrong TLS certificate

CVE-2026-61813 · published 16 days ago
Summary

The ModSecurity web firewall versions before 2.9.15 and 3.0.17 do not check the server name tightly when downloading files over HTTPS. This can allow a man‑in‑the‑middle attacker to trick the system into trusting a certificate that belongs to a different site. Update ModSecurity to version 2.9.15 or later (or 3.0.17 or later) to enforce the correct check.

What to do
  • Update modsecurity to version 3.0.17.
  • Update modsecurity2 to version 3.0.17.
Affected software
Ecosystem VendorProductAffected versions
– owasp-modsecurity modsecurity < 2.9.15
Debian:12 debian modsecurity All versions
Debian:13 debian modsecurity All versions
Debian:14 debian modsecurity All versions
Debian:12 debian modsecurity-apache All versions
Debian:13 debian modsecurity-apache All versions
Debian:14 debian modsecurity-apache All versions
Ubuntu:Pro:14.04:LTS canonical modsecurity-apache All versions
Ubuntu:20.04:LTS canonical modsecurity All versions
Bitnami – modsecurity >= 3.0.0, < 3.0.17
Fix: upgrade to 3.0.17
Bitnami – modsecurity2 >= 3.0.0, < 3.0.17
Fix: upgrade to 3.0.17
Original advisory text
ModSecurity: Incorrect libcurl TLS hostname verification setting in HttpsClient::download
ModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx. Prior to 2.9.15 and 3.0.17, the HttpsClient::download function in src/utils/https_client.cc sets libcurl CURLOPT_SSL_VERIFYHOST to 1 instead of the strict value 2L. Under adversary-in-the-middle and TLS interception conditions, this non-strict setting may weaken TLS peer identity validation and increase the risk of accepting a certificate for an unintended host. End-to-end exploitation is non-trivial in typical environments. This issue is fixed in versions 2.9.15 and 3.0.17.
Fix within
Internet-facing 60 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker partial control
Severity
3.7 Low
Exploitation
<1% chance of attack within 30 days
Type
CWE-295Improper Certificate Validation
Timeline
Published5 Nov 2026
Updated18 Nov 2026
First seen1 Oct 2026
Track software like this
Free during beta