CVE & CISA-KEV Catalog

CVE-2026-56387

HIGH
7.5
CVSS v3
NVD

Description

The RTMP AMF parser in Apache bRPC accepts AMF string lengths and array counts directly from untrusted input. A remote unauthenticated attacker who can reach a bRPC server with RTMP enabled can send a small AMF payload with an excessive declared long string length or array count, causing excessive memory allocation or resource consumption before the parser rejects the incomplete payload. Root Cause: The AMF long string parser resized the destination string to the declared 32-bit length before validating that the stream contained that many bytes. ECMA array and strict array parsers also accepted 32-bit element counts without a configurable upper bound. Affected Scenarios: Deployments that enable the bRPC RTMP server component and accept RTMP traffic from untrusted clients. Direct uses of the AMF parser on untrusted data are also affected. How to Fix: 1. Upgrade bRPC to version 1.18.0, which fixes this issue. 2. Apply this patch: https://github.com/apache/brpc/pull/3353 Note: The fix introduces configurable AMF parsing limits. The default maximum string size is 64 MiB and the default maximum array element count is 1,048,576. Payloads above these limits are rejected. The limits can be adjusted with amf_max_string_size and amf_max_array_size.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged

Impact

ConfidentialityNone
IntegrityNone
AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploit Intelligence

0.60%probability of exploitation in 30 days
49thpercentile

Moderate risk: more likely to be exploited than 49% of all known CVEs.

References

Other references1

Related Vulnerabilities

Other CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2023-50387High7.5100%-Fix
CVE-2019-11478Medium5.394%-Fix
CVE-2019-11479High7.591%-Fix
CVE-2022-30522High7.590%-Fix
CVE-2024-27316High7.589%-Fix
CVE-2019-9515High7.588%-Fix

Common questions

How do I fix CVE-2026-56387?

No published fix for CVE-2026-56387 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2026-56387 being actively exploited?

Not that we know of. CVE-2026-56387 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.60% is the estimated probability that it will be exploited in the next 30 days. That is higher than 49% of all scored CVEs.

How severe is CVE-2026-56387?

CVE-2026-56387 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2026-56387
CVE-2026-56387 severity badge

Markdown

[![CVE-2026-56387](https://tridentstack.com/cve/badge/CVE-2026-56387.svg)](https://tridentstack.com/cve/CVE-2026-56387)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-56387"><img src="https://tridentstack.com/cve/badge/CVE-2026-56387.svg" alt="CVE-2026-56387"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

Run a free CVE scan on your fleetStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-30.