CVE-2026-61902
N/AApache bRPC versions before 1.18.0 do not consistently enforce the configured max_body_size limit in non-progressive HTTP/1 and HTTP/2 parsing and in memcache and couchbase response parsing. A remote unauthenticated peer can cause an affected process to buffer message data beyond the configured limit, which may lead to memory exhaustion and denial of service. Users should upgrade to 1.18.0 or apply the patch from PR https://github.com/apache/brpc/pull/3382 . The fix rejects oversized buffered HTTP bodies, returns HTTP 413 for HTTP/1 requests, resets oversized HTTP/2 streams, and rejects oversized memcache and couchbase responses from their declared lengths. Progressive HTTP reading remains supported because it uses bounded buffering.
No known exploitation, public exploit, or elevated probability at this time. Track for changes.
Exploitation likelihood
0.2%chance of exploitation in 30 days · 5th percentile
Impact if exploited
—CVSS · not scored
- No impact metrics
Proof of concept
No public PoC is currently catalogued.
Search for new PoCs
Search GitHub now — results may be empty or unverified.
Tracked sources are checked daily for recent CVEs, including PoCs published after the original disclosure. A later release appears after a tracked source lists it and a refresh succeeds.
Data snapshot:
Weakness (CWE)
- CWE-400: Uncontrolled Resource Consumption
CVSS vector
Not yet scored.
References and research data (JSON)
References
Advisories
- https://lists.apache.org/thread/2pf15ojj0vr7rtx95677kgtl1mx3gdgb CVE record · apache · Updated 2026-10-21T11:41:56.277Z
NVD · CVE-2026-61902 · Updated 2026-10-22T16:56:37.023 - https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-107176 EUVD · EUVD-2026-107176