{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-56387 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-56387 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-56387 is a vulnerability in Apache bRPC, published on 21 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-56387 and fix it if it is affected.\n\nWhat it is: CVE-2026-56387 is a vulnerability in Apache bRPC, published on 21 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-56387 in the wild and no public exploit code.\n\nAffected product: Apache bRPC. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-56387/ (Markdown: https://insights.sbomify.com/CVE-2026-56387/index.md)","id":"CVE-2026-56387","markdown":"https://insights.sbomify.com/CVE-2026-56387/index.md","name":"CVE-2026-56387","record":{"aliases":["GHSA-79v7-r95h-fxr5"],"analysis":null,"analysis_generated_by":null,"assigner":"apache","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[{"id":"CWE-789","name":"Memory Allocation with Excessive Size Value"},{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"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.\n\nRoot Cause:\nThe 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.\n\nAffected Scenarios:\nDeployments 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.\n\nHow to Fix:\n1. Upgrade bRPC to version 1.18.0, which fixes this issue.\n2. Apply this patch:  https://github.com/apache/brpc/pull/3353 \n\nNote:\nThe 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Apache bRPC: Remote Memory Exhaustion in RTMP AMF Parser","id":"CVE-2026-56387","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Apache bRPC: Out-of-Bounds Write in Redis Command Parser","id":"CVE-2026-56388"},"packages":[],"prev":{"headline":"Apache bRPC: Integer Underflow and Out-of-Bounds Read in HTTP/2 DATA Frame Parser","id":"CVE-2026-56386"},"products":["Apache bRPC"],"published":"2026-10-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Apache Software Foundation"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-56387/"}