CVE-2026-78048
Deferred Deferred - Pending Action

Reachable Assertion in Apache bRPC HPACK Decoder

Vulnerability report for CVE-2026-78048, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-21

Last updated on: 2026-10-30

Assigner: Apache Software Foundation

Description

A reachable-assertion flaw in the HPACK header-compression decoder of the HTTP/2 (h2/gRPC) stack in Apache bRPC (version < 1.18.0) on all platforms allows a remote attacker to crash the server process by sending a crafted sequence of HPACK headers, resulting in a denial of service. Root Cause: In src/brpc/details/hpack.cpp, IndexTable::Init sizes the dynamic-table ring buffer as num_headers = max_size / (32 + 2), i.e. it assumes a minimum table entry of 34 bytes (name >= 1 byte + value >= 1 byte + 32 bytes of overhead). However, RFC 7541 section 4.1 specifies that the minimum entry size is 33 bytes, because the value may be empty (name >= 1 byte + value == 0 + 32 bytes). For the default 4096-byte table this allocates only 120 slots (4096/34). Eviction in AddHeader is driven by byte usage (_max_size), not by slot count, so a peer can add 121 minimal 33-byte entries (121*33 = 3993 <= 4096) without triggering eviction. The 121st AddHeader then hits CHECK(!_header_queue.full()), which aborts the process. Affected Scenarios: Use a bRPC server that serves HTTP/2 or gRPC requests (e.g. via the h2 protocol) from an untrusted network. The malicious header block is processed during HPACK decoding of incoming requests without authentication. How to Fix: (Choose one of the following options)Β  1. Upgrade bRPC to version 1.18.0, which fixes this issue. 2. Apply this patch:Β https://github.com/apache/brpc/pull/3462 Note: The fix sizes the dynamic table for the 33-byte minimum entry (max_size / (32 + 1)) and ensures at least one ring-buffer slot is kept when max_size is smaller than the minimum entry, so that initialization cannot fail on malloc(0).

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-21
Last Modified
2026-10-30
Generated
2026-11-10
AI Q&A
2026-10-21
EPSS Evaluated
2026-11-09
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Apache Software Foundation Apache bRPC 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-617 The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a reachable-assertion flaw in the HPACK header-compression decoder of the HTTP/2 (h2/gRPC) stack in Apache bRPC versions before 1.18.0. A remote attacker can crash the server process by sending a specially crafted sequence of HPACK headers, causing a denial of service.

Detection Guidance

This vulnerability can be detected by monitoring for crashes in bRPC server processes handling HTTP/2 or gRPC requests. Check server logs for assertion failures in hpack.cpp or abnormal terminations during HPACK header processing.

Impact Analysis

If you operate a bRPC server handling HTTP/2 or gRPC requests from untrusted networks, an attacker could exploit this to crash the server, disrupting service availability. The attack requires no authentication and targets the HPACK decoding process during request handling.

Compliance Impact

This vulnerability causes a denial of service by crashing the server process, which could disrupt services handling sensitive data. For GDPR, this may lead to service unavailability, potentially violating data processing requirements. For HIPAA, it could interrupt critical healthcare services, risking compliance with availability standards.

Mitigation Strategies
  • Upgrade bRPC to version 1.18.0 or later to address the flaw.
  • Apply the patch from https://github.com/apache/brpc/pull/3462 if upgrading is not immediately possible.
  • Restrict access to HTTP/2 or gRPC endpoints to trusted networks only.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-78048. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...