LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22776: cpp-httplib vulnerable to a denial of service (DOS) using a zip bomb

cpp-httplib is a C++11 single-file header-only cross platform HTTP/HTTPS library. Prior to version 0.30.1, a Denial of Service (DoS) vulnerability exists in cpp-httplib due to the unsafe handling of compressed HTTP request bodies (Content-Encoding: gzip, br, etc.). The library validates the payload_max_length against the compressed data size received from the network, but does not limit the size of the decompressed data stored in memory.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-22776 can let an unauthenticated remote requester exhaust memory in applications using vulnerable cpp-httplib versions. The issue involves compressed request bodies that expand much larger after decompression. Business impact is service disruption, not data theft or code execution based on available sources.

Executive priority

Treat as a high-priority availability risk for internet-facing C++ services using cpp-httplib. Patch promptly where the library is embedded, especially in customer-facing APIs or services with strict uptime requirements.

Technical view

cpp-httplib before 0.30.1 checks payload_max_length against compressed network input but does not cap decompressed data stored in memory. This creates a CWE-409 zip bomb denial-of-service condition over HTTP/HTTPS. CVSS v4.0 is 8.7, with high availability impact and no privileges or user interaction required.

Likely exposure

Exposure is likely where products or internal services embed yhirose cpp-httplib before 0.30.1 and accept compressed HTTP request bodies such as gzip or br. Header-only use may make detection harder because the library can be vendored directly into source trees.

Exploitation context

Sources do not indicate active exploitation, and the CVE is not marked in KEV. Exploitation requires network access to an affected service that processes compressed request bodies. The practical result is availability loss through memory exhaustion.

Researcher notes

The key validation point is whether payload limits apply after decompression, not only to compressed input size. Review the GitHub advisory and patch commit for implementation details. No source in the bundle claims confidentiality, integrity, code execution, or active exploitation.

Mitigation direction

  • Upgrade cpp-httplib to version 0.30.1 or later.
  • Search source and vendored dependencies for embedded cpp-httplib copies.
  • Prioritize internet-facing services that accept HTTP request bodies.
  • If upgrade is delayed, follow the GitHub advisory for vendor-supported guidance.

Validation and detection

  • Confirm deployed cpp-httplib version is 0.30.1 or later.
  • Check build artifacts and repositories for vendored httplib headers.
  • Identify endpoints that accept compressed HTTP request bodies.
  • Review service monitoring for memory exhaustion or abnormal request-driven crashes.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-409: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22776 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2026-22776Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
yhirosecpp-httplib< 0.30.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-409 · source CWE mapping

Improper Handling of Highly Compressed Data (Data Amplification)

Improper Handling of Highly Compressed Data (Data Amplification) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.