{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-82231 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-82231 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-82231 is a vulnerability in Apache bRPC, published on 21 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-82231 and fix it if it is affected.\n\nWhat it is: CVE-2026-82231 is a vulnerability in Apache bRPC, published on 21 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-82231 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-82231/ (Markdown: https://insights.sbomify.com/CVE-2026-82231/index.md)","id":"CVE-2026-82231","markdown":"https://insights.sbomify.com/CVE-2026-82231/index.md","name":"CVE-2026-82231","record":{"aliases":["GHSA-4xj2-88x8-3w8g"],"analysis":null,"analysis_generated_by":null,"assigner":"apache","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[{"id":"CWE-248","name":"Uncaught Exception"}],"description":"A Thrift client in Apache bRPC (version \u003c 1.18.0, built with WITH_THRIFT which is off by default) can be crashed by the server peer it talks to. When the server returns a T_EXCEPTION reply whose exception struct is malformed, the client decodes it without catching what Apache Thrift throws (TProtocolException, TTransportException or std::length_error). The exception unwinds out of the bthread task function and the process calls std::terminate(), terminating the whole process along with every other in-flight RPC.\n\nThis is the client response path, so the adversary is the server peer, which THREAT_MODEL.md treats as untrusted. It requires a WITH_THRIFT build (off by default).\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/3500","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: Malformed Thrift T_EXCEPTION reply causes process termination in Thrift client","id":"CVE-2026-82231","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 Syncope: SQL injection via sort parameter in Task search","id":"CVE-2026-82232"},"packages":[],"prev":{"headline":"Apache bRPC: Stack Exhaustion via Unbounded Recursion in mcpack2pb Parser","id":"CVE-2026-82230"},"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-82231/"}