CVE-2026-32627
Awaiting Analysis Awaiting Analysis - Queue
TLS Verification Bypass in cpp-httplib HTTPS Redirects Enables MITM

Publication date: 2026-03-16

Last updated on: 2026-03-17

Assigner: GitHub, Inc.

Description
cpp-httplib is a C++11 single-file header-only cross platform HTTP/HTTPS library. Prior to 0.37.2, when a cpp-httplib client is configured with a proxy and set_follow_location(true), any HTTPS redirect it follows will have TLS certificate and hostname verification silently disabled on the new connection. The client will accept any certificate presented by the redirect target β€” expired, self-signed, or forged β€” without raising an error or notifying the application. A network attacker in a position to return a redirect response can fully intercept the follow-up HTTPS connection, including any credentials or session tokens in flight. This vulnerability is fixed in 0.37.2.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-16
Last Modified
2026-03-17
Generated
2026-05-07
AI Q&A
2026-03-16
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
yhirose cpp-httplib to 0.37.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-295 The product does not validate, or incorrectly validates, a certificate.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2026-32627 is a high-severity vulnerability in the cpp-httplib C++ HTTP/HTTPS library versions up to 0.37.1. When a cpp-httplib client is configured to use a proxy and has redirect following enabled (set_follow_location(true)), the TLS certificate and hostname verification are silently disabled on HTTPS redirects. This means the client will accept any TLS certificate presented by the redirect targetβ€”including expired, self-signed, or forged certificatesβ€”without raising any error or notifying the application.

The root cause is that when following a redirect through a proxy, the library forcibly disables server certificate and hostname verification on the new SSL connection, unlike the non-proxy path which preserves the original verification settings. Additionally, all authentication credentials are copied to the redirect client before verification is disabled, exposing sensitive data over an unverified TLS connection.


How can this vulnerability impact me? :

This vulnerability allows a network attacker who can control or intercept the redirect response, proxy, or DNS resolution to fully intercept the follow-up HTTPS connection. Because TLS verification is disabled, the attacker can present any certificate and the client will accept it silently.

As a result, the attacker can read and modify all data transmitted over the connection, including sensitive credentials and session tokens. This compromises the confidentiality and integrity of the communication, potentially leading to unauthorized access, data theft, or session hijacking.

The vulnerability is particularly relevant in environments where proxies and redirects are common, such as corporate networks and IoT deployments.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability occurs when a cpp-httplib client is configured with a proxy and set_follow_location(true), causing TLS certificate and hostname verification to be silently disabled on HTTPS redirects. Detection involves identifying cpp-httplib clients using versions prior to 0.37.2 with proxy and redirect following enabled.

To detect exploitation or presence of this vulnerability on your network or system, you can monitor for HTTPS redirect responses followed by TLS connections that accept invalid certificates without errors or warnings.

Suggested commands include using network traffic analysis tools like tcpdump or Wireshark to capture and inspect HTTPS redirect flows and TLS handshakes for certificate validation failures or acceptance of self-signed/expired certificates.

  • Use tcpdump to capture traffic on the relevant interface: tcpdump -i <interface> -w capture.pcap
  • Analyze the capture with Wireshark to look for HTTP 3xx redirect responses followed by TLS handshakes that accept invalid certificates.
  • Check application logs or enable verbose logging in cpp-httplib clients to detect if certificate verification is disabled during redirects.

What immediate steps should I take to mitigate this vulnerability?

The primary mitigation is to upgrade the cpp-httplib library to version 0.37.2 or later, where the vulnerability is fixed by preserving SSL verification settings when following HTTPS redirects through a proxy.

If upgrading immediately is not possible, temporarily disable the use of proxies or the set_follow_location(true) option in cpp-httplib clients to avoid triggering the vulnerable code path.

Additionally, review and monitor network traffic for suspicious redirects and TLS connections that may indicate exploitation attempts.

  • Upgrade cpp-httplib to version 0.37.2 or later.
  • Disable proxy configuration or set_follow_location(true) in the client until the patch is applied.
  • Implement network monitoring to detect suspicious redirect and TLS handshake behavior.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart