Skip to main content
VulnerabilityPublished Updated

CVE-2026-56387: Apache bRPC accepts AMF string lengths · RTMP AMF Parser

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-56387· 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:17 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

Upgrade Apache bRPC to version 1.18.0 or later, which fixes this vulnerability by introducing configurable limits on AMF parsing. The default limits are a maximum string size of 64 MiB and a maximum array element count of 1,048,576. Payloads exceeding these limits are rejected. These limits can be adjusted via the amf_max_string_size and amf_max_array_size settings. No other mitigation is required once the upgrade is applied.

Description

Apache bRPC's RTMP AMF parser improperly accepts AMF string lengths and array counts directly from untrusted input without sufficient validation. This allows a remote unauthenticated attacker to send a crafted AMF payload with excessive declared sizes, causing excessive memory allocation or resource consumption, potentially leading to denial of service. The issue affects deployments with RTMP enabled and untrusted client traffic. The vulnerability is fixed in bRPC version 1.18.0, which introduces configurable limits on AMF parsing to prevent such attacks.

References

Community reviews

Loading reviews…