CVE-2026-82230
Last modified
CVE-2026-82230 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. Uncontrolled recursion in the mcpack2pb component in Apache bRPC (version < 1.18.0) on all platforms allows remote attackers to make the server crash via sending deeply nested mcpack data. Root Cause: The bRPC mcpack2pb parser (used to serve nshead_mcpack / ubrpc / public_pbrpc requests) recursively parses nested objects and arrays without any depth limit. For a protobuf message that references itself (e.g. EPSS estimates a 0.55% chance of exploitation in the next 30 days.
Description
Uncontrolled recursion in the mcpack2pb component in Apache bRPC (version < 1.18.0) on all platforms allows remote attackers to make the server crash via sending deeply nested mcpack data. Root Cause: The bRPC mcpack2pb parser (used to serve nshead_mcpack / ubrpc / public_pbrpc requests) recursively parses nested objects and arrays without any depth limit. For a protobuf message that references itself (e.g. a repeated message field), the generated parser recurses once per nesting level of the incoming mcpack object. A deeply nested request makes the recursion grow unbounded, overflow the stack and crash the process. Affected Scenarios: Use bRPC server with a recursive-schema protobuf message to serve nshead_mcpack / ubrpc / public_pbrpc requests from untrusted network. How to Fix: (Choose one of the following options) 1. Upgrade bRPC to version 1.18.0, which fixes this issue. 2. Apply this patch: https://github.com/apache/brpc/pull/3499 Note: No matter which option you choose, you should know that the fix enforces the documented parsing depth limit MAX_DEPTH (128) on the parse path, the same limit the serializer already applies. If your requests contain mcpack messages nested deeper than 128 levels, the request will be failed after applying the fix.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Apache Software Foundation | Apache bRPC | < 1.18.0 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-82230?
How severe is CVE-2026-82230?
How do I fix CVE-2026-82230?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-82225Unauthenticated Broken Authentication in RegistrationMagic <…7.4
- CVE-2026-82226Unauthenticated PHP Object Injection in Tickera <= 3.6.0.2 v…9.8
- CVE-2026-82227Contributor SQL Injection in WPBulky <= 1.2.2 versions.8.5
- CVE-2026-82228Unauthenticated Bypass Vulnerability in SiteGround Security …8.1
- CVE-2026-82229Unauthenticated Cross Site Scripting (XSS) in WordPress Soci…7.1
- CVE-2026-8223A vulnerability was found in Open5GS up to 2.7.7. Affected b…7.5
- CVE-2026-82231A Thrift client in Apache bRPC (version < 1.18.0, built with…
- CVE-2026-82232Improper neutralization of special elements used in an SQL c…9.8
- CVE-2026-82233SiYuan before v3.8.1 contains a path traversal vulnerability…5.7
- CVE-2026-82234SiYuan versions before v3.8.1 contain a server-side request …8.2
- CVE-2026-82235filebrowser through 2.63.23 fails to validate named pipes in…5.9
- CVE-2026-82236File Browser versions from 2.63.6 through 2.63.23 fail to cl…3.1
Are you affected by CVE-2026-82230?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
