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 | Vendor | Product | Affected 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.
References
- https://github.com/owasp-modsecurity/ModSecurity/commit/cce204806430e4848327aade... URL
- https://github.com/owasp-modsecurity/ModSecurity/security/advisories/GHSA-2vqc-3... URL
- https://github.com/owasp-modsecurity/ModSecurity/commit/edca70d853bfb725325137fa... URL
- https://github.com/owasp-modsecurity/ModSecurity/releases/tag/v2.9.15 URL
- https://github.com/owasp-modsecurity/ModSecurity/releases/tag/v3.0.17 URL
- https://security-tracker.debian.org/tracker/CVE-2026-61813 Vendor Advisory
- https://ubuntu.com/security/CVE-2026-61813 Third Party Advisory
- https://www.cve.org/CVERecord?id=CVE-2026-61813 Third Party Advisory
- https://github.com/advisories/GHSA-2vqc-36qp-ccmw Third Party Advisory
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/61xxx/CVE-2026-61813... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-61813 URL
- https://modsecurity.org/20260928/security-update-digest-overview-of-recent-advis... Third Party Advisory
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
Type
CWE-295Improper Certificate Validation
Timeline
Published5 Nov 2026
Updated18 Nov 2026
First seen1 Oct 2026
Sources
DEBIAN-CVE-2026-61813 · OSV
UBUNTU-CVE-2026-61813 · OSV
CVE-2026-61813 · NVD
CVE-2026-61813 · MITRE
CVE-2026-61813 · OSV
GHSA-2vqc-36qp-ccmw · GHSA
Track software like this
Free during beta