Skip to main content
CVE-2026-61902VulnerabilityPublished Updated

Apache bRPC versions before 1.18.0 do not consistently enforce the configured max_body_size limit in non-progressive

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-61902· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 1.18.0 soon.

Data as of 30 Oct 2026, 17:18 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.17.5
Patch
Available – fixed in 1.18.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Apache bRPC and apache/brpc to 1.18.0.

Affected software

ProductAffectedFixed in
Apache bRPCapache/brpcAffected
  • <1.18.0
Fixed in
  • 1.18.0
GitHubapache/brpcpkg:github/apache/brpcOther threatsAffected
  • <1.18.0
Fixed in
  • 1.18.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade to Apache bRPC version 1.18.0 or later, which contains the official fix for this vulnerability. The fix enforces max_body_size limits consistently and rejects oversized requests and responses. No other mitigation is indicated or required.

Description

Apache bRPC versions before 1.18.0 have a vulnerability where the configured max_body_size limit is not consistently enforced in certain HTTP and response parsing scenarios. This allows a remote unauthenticated attacker to cause memory exhaustion by sending oversized message data, leading to denial of service. The issue is fixed in version 1.18.0, which properly rejects oversized HTTP bodies and responses.

References

Community reviews

Loading reviews…