Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-56386 Overview
CVE-2026-56386 is an integer underflow and out-of-bounds read vulnerability in the HTTP/2 server DATA frame parser in Apache bRPC. An unauthenticated remote attacker can trigger a denial of service by sending a malformed HTTP/2 DATA frame with the PADDED flag set and a zero-length payload. The flaw affects any Apache bRPC server that accepts HTTP/2 traffic, whether through cleartext h2c detection on an HTTP port or through TLS ALPN negotiation. The issue is tracked under [CWE-125] (Out-of-bounds Read) and is fixed in Apache bRPC 1.18.0.
Critical Impact
Unauthenticated remote attackers can crash Apache bRPC HTTP/2 servers by sending a single malformed DATA frame, disrupting availability of RPC services.
Affected Products
- Apache bRPC versions prior to 1.18.0
- Apache bRPC HTTP/2 servers reachable via cleartext h2c on an HTTP port
- Apache bRPC HTTP/2 servers reachable via TLS with ALPN negotiation
Discovery Timeline
- 2026-10-21 - CVE-2026-56386 published to the National Vulnerability Database
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-56386
Vulnerability Analysis
The vulnerability lives in the HTTP/2 DATA frame handling path of Apache bRPC. HTTP/2 DATA frames may carry an optional PADDED flag that signals the presence of a one-byte pad length field at the start of the payload, followed by padding bytes at the end. The bRPC parser computed the fragment size directly from the attacker-controlled frame payload length. When the PADDED flag was present, the parser decremented the fragment size to account for the pad length byte without first verifying that any payload bytes existed.
Sending a DATA frame with the PADDED flag set and a payload length of zero causes the unsigned fragment size to underflow to a very large value. The parser then reads the pad length byte from memory beyond the end of the frame buffer. The resulting out-of-bounds read causes the server process to abort, denying service to all connected clients.
Root Cause
The root cause is missing input validation on the DATA frame payload length prior to arithmetic that assumes a mandatory pad length byte is present. The unsigned integer underflow combined with the subsequent out-of-bounds read maps directly to [CWE-125]. The parser trusted the attacker-supplied length field without enforcing the HTTP/2 protocol requirement that a padded frame contain at least one payload byte for the pad length field.
Attack Vector
Exploitation requires only network reach to an Apache bRPC HTTP/2 listener. No authentication, user interaction, or prior access is needed. An attacker establishes an HTTP/2 connection, either through h2c upgrade on a plaintext HTTP port or through TLS ALPN selection of h2, then transmits a single DATA frame with the PADDED flag set (0x08) and a payload length of zero. The server underflows the fragment size calculation and performs the out-of-bounds read, terminating the server process.
No verified public proof-of-concept code is available. The protocol-level trigger is described in the Apache Security Discussion and the upstream patch.
Detection Methods for CVE-2026-56386
Indicators of Compromise
- Unexpected Apache bRPC server crashes or restarts correlated with inbound HTTP/2 traffic
- HTTP/2 DATA frames with the PADDED flag (0x08) set and a payload length of zero in network captures
- Repeated h2c upgrade requests or TLS ALPN negotiations for h2 from untrusted sources immediately preceding service outages
- Core dumps or segmentation fault entries in bRPC server logs referencing the HTTP/2 DATA frame parser
Detection Strategies
- Deploy network-based intrusion detection signatures that flag HTTP/2 DATA frames where the PADDED flag is set and the frame length equals zero
- Monitor Apache bRPC process health metrics and alert on abnormal restart counts
- Enable verbose protocol logging on front-end load balancers that terminate HTTP/2 to capture malformed frame events
- Correlate FRAME_SIZE_ERROR responses from patched servers with source IPs to identify active probing
Monitoring Recommendations
- Track Apache bRPC server uptime and crash telemetry through centralized logging
- Ingest HTTP/2 frame metadata from reverse proxies into a SIEM for anomaly detection
- Alert on inbound HTTP/2 connections from unexpected source networks to internal RPC services
How to Mitigate CVE-2026-56386
Immediate Actions Required
- Inventory all Apache bRPC deployments and identify versions prior to 1.18.0
- Upgrade affected servers to Apache bRPC 1.18.0 as the primary remediation
- Restrict network exposure of bRPC HTTP/2 listeners to trusted clients until patching completes
- Disable h2c cleartext upgrade on public-facing HTTP ports where HTTP/2 is not required
Patch Information
Upgrade to Apache bRPC 1.18.0, which validates that a padded DATA frame contains enough payload bytes for the pad length field before decrementing the fragment size or reading the pad length byte. Malformed zero-length padded DATA frames are rejected with FRAME_SIZE_ERROR. Organizations unable to upgrade immediately can apply the upstream fix from Apache bRPC pull request #3325. Additional context is available in the Apache Security Discussion thread.
Workarounds
- Terminate HTTP/2 at a hardened reverse proxy that rejects malformed DATA frames before they reach the bRPC server
- Disable HTTP/2 support on bRPC endpoints and serve only HTTP/1.1 where feasible
- Enforce network ACLs limiting HTTP/2 access to authenticated client subnets
- Deploy rate limiting and connection quotas on upstream load balancers to reduce blast radius of crash-loop attempts
# Example: restrict inbound HTTP/2 access to trusted subnets using iptables
iptables -A INPUT -p tcp --dport 8080 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p tcp --dport 8080 -j DROP
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

