
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2026-61813 is an improper certificate validation vulnerability in ModSecurity, an open-source cross-platform WAF engine for Apache, IIS, and Nginx. The flaw exists in the HttpsClient::download function (and the related msc_remote_download_content function in the Apache2 branch), where CURLOPT_SSL_VERIFYHOST is incorrectly set to 1 instead of the strict value 2L, weakening TLS hostname verification. Affected versions include all ModSecurity 2.x releases prior to 2.9.15 and 3.x releases from 3.0.0 up to (but not including) 3.0.17. The vulnerability was disclosed on September 30, 2026, and fixed releases were published the same day. It carries a CVSS v3.1 base score of 3.7 (Low) (GitHub Advisory, Feedly).
The root cause is classified as CWE-295 (Improper Certificate Validation). In src/utils/https_client.cc (v3 branch) and apache2/msc_remote_rules.c (v2 branch), the libcurl option CURLOPT_SSL_VERIFYHOST is set to 1, which in libcurl only checks that the server certificate contains a Common Name field — it does not verify that the CN matches the requested hostname. The correct strict value is 2L, which enforces full hostname matching. An attacker positioned as an adversary-in-the-middle (AiTM) with TLS interception capability could present a valid certificate for an arbitrary host, and ModSecurity would accept it as legitimate during remote rule downloads. The fix, applied in commits cce2048 (v3) and edca70d (v2), changes the single-line setting to curl_easy_setopt(curl, CURLOPT_SSL_VERIFYHOST, 2L) (GitHub Advisory, Patch v3, Patch v2).
Successful exploitation allows an unauthenticated attacker with an AiTM network position to intercept ModSecurity's outbound HTTPS connections used for downloading remote rule sets, and substitute a rogue server presenting a certificate for an unintended host. This could result in ModSecurity loading attacker-controlled WAF rules, potentially disabling protections or introducing malicious rule logic, and may expose sensitive data transmitted during the TLS session. The impact is limited to confidentiality (low) with no direct integrity or availability impact assessed by the CVSS score, though the downstream consequence of loading tampered rules could be significant (GitHub Advisory, Feedly).
No public proof-of-concept exploit code exists, and there is no evidence of in-the-wild exploitation as of the disclosure date. The EPSS score is approximately 0.155%, reflecting a low probability of exploitation in the near term. Exploitation requires an attacker to hold an AiTM network position with TLS interception capability, making opportunistic exploitation non-trivial. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog, and NVD's SSVC assessment classifies exploitation as "none" and automation as "no" (GitHub Advisory, Feedly).
SecRemoteRules or equivalent configuration pointing to an HTTPS endpoint).CURLOPT_SSL_VERIFYHOST is set to 1, libcurl will not verify that the certificate's CN/SAN matches the target hostname..conf or .rules files with unknown origins.Upgrade ModSecurity to version 2.9.15 (v2 branch) or 3.0.17 (v3 branch), which correct CURLOPT_SSL_VERIFYHOST to the strict value 2L in both src/utils/https_client.cc and apache2/msc_remote_rules.c. As an interim workaround where upgrading is not immediately possible, disable remote rule downloads (SecRemoteRules) and use only locally hosted rule sets, or implement network-layer controls (e.g., strict egress filtering, TLS inspection with pinned certificates) to prevent AiTM attacks on the ModSecurity host's outbound connections (v2.9.15 Release, v3.0.17 Release).
The vulnerability was reported by researcher amitu314 and coordinated through GitHub's private security advisory process before public disclosure. Red Hat has tracked the issue via Bugzilla (bug #2567914). Community discussion has been limited given the low severity score and non-trivial exploitation requirements, with some blog posts on dev.to noting the issue in the context of the broader ModSecurity September 2026 patch batch (Red Hat Bugzilla, GitHub Advisory).
Fix availability across major Linux distributions and their releases.
bookworm
modsecurity-apache
sid
modsecurity-apache
trixie
modsecurity-apache
bionic (esm-apps)
modsecurity-apache
devel
modsecurity
focal (esm-apps)
modsecurity
jammy
modsecurity
jammy (esm-apps)
modsecurity
noble
modsecurity
noble (esm-apps)
modsecurity
resolute
modsecurity
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."