CVE-2026-56387: CWE-789 Memory Allocation with Excessive Size Value in Apache Software Foundation Apache bRPC
Description
CVE-2026-56387 is a vulnerability in Apache bRPC's RTMP AMF parser where untrusted input can specify excessive string lengths or array counts, leading to excessive memory allocation or resource consumption. This affects deployments with the bRPC RTMP server enabled and accepting RTMP traffic from untrusted clients. The issue is fixed in Apache bRPC version 1.18.0 by introducing configurable limits on AMF string size and array element count.
Affected software
Apache Software Foundation
Apache bRPC
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The RTMP AMF parser in Apache bRPC accepts AMF string lengths and array counts directly from untrusted input without sufficient validation. Specifically, the parser resizes the destination string to the declared 32-bit length before verifying the stream contains that many bytes. Similarly, ECMA and strict array parsers accept 32-bit element counts without an upper bound. This can cause excessive memory allocation or resource consumption when processing crafted payloads. The vulnerability affects bRPC versions prior to 1.18.0 where the RTMP server component is enabled. The issue is addressed in version 1.18.0 by adding configurable maximum limits for string size (default 64 MiB) and array size (default 1,048,576 elements), rejecting payloads exceeding these limits.
Potential Impact
A remote unauthenticated attacker able to send RTMP traffic to a vulnerable bRPC server can cause excessive memory allocation or resource consumption, potentially leading to denial of service conditions. The vulnerability arises before the parser rejects incomplete payloads, allowing resource exhaustion attacks.
Mitigation Recommendations
Upgrade Apache bRPC to version 1.18.0 or later, which includes the fix introducing configurable limits on AMF string and array sizes. The default limits reject payloads with string sizes over 64 MiB and array counts over 1,048,576 elements. Adjust these limits as needed using the amf_max_string_size and amf_max_array_size configuration options. No other mitigation is indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-06-21T04:46:23.974Z
- State
- PUBLISHED
Threat ID: 6ad8a6b32cdf04f656e8130e
Added to database: 10/21/2026, 11:49:07 UTC
Last enriched: 10/21/2026, 12:04:32 UTC
Last updated: 10/21/2026, 13:40:20 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.