Skip to content
Fencer Intel
low 3.7

CVE-2026-61813 json

ModSecurity: Incorrect libcurl TLS hostname verification setting in HttpsClient::download

published last mo. modified 2d ago also EUVD-2026-117553 , GHSA-2vqc-36qp-ccmw

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository owasp-modsecurity/ModSecurity. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
3.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 4%
public exploits
0
none known

Summary

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.

Patch / fix

  • trustwave modsecurity 2.9.15, 3.0.17
  • owasp modsecurity 2.9.15, 3.0.17
  • owasp owasp_modsecurity 2.9.15, 3.0.17
  • owasp libmodsecurity 2.9.15, 3.0.17

Is CVE-2026-61813 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-61813 updated cvss 3.7

mod_security: modsecurity: ModSecurity: Weak TLS certificate validation via improper hostname verification

  • Red Hat Enterprise Linux 7 mod_security-mlogc, mod_security 2.9.14-1.el10 Red Hat Enterprise Linux 8 mod_security, mod_security-mlogc, mod_security 2.9.14-1.el10 Red Hat Enterprise Linux 9 mod_security, mod_security-mlogc, mod_security 2.9.14-1.el10 Red Hat Enterprise Linux 10 mod_security 2.9.14-1.el10 Red Hat JBoss Core Services jbcs-httpd24-mod_security, jbcs-httpd24-mod_security-src-zip
    under investigation

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2d ago

Exploit prediction

0.16% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

  • owasp-modsecurity ModSecurity

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of owasp-modsecurity/ModSecurity published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.