CVE-2026-87849
Last modified
CVE-2026-87849 is a vulnerability of currently unknown severity. The Discovery naming-service reply parser in Apache bRPC (versions < 1.18.0) calls RapidJSON object-only accessors (FindMember) on JSON values without first validating that those values are objects. A malformed Discovery response whose data/service members or instances list contain non-object entries (e.g. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
The Discovery naming-service reply parser in Apache bRPC (versions < 1.18.0) calls RapidJSON object-only accessors (FindMember) on JSON values without first validating that those values are objects. A malformed Discovery response whose data/service members or instances list contain non-object entries (e.g. a bare integer) triggers the RapidJSON object-access precondition on the client, reading memory out of bounds and potentially crashing the bRPC client. Root Cause: In src/brpc/policy/discovery_naming_service.cpp, DiscoveryNamingService::GetServers() and DiscoveryNames::ListDiscoveryNodes() access JSON values with member functions on non-object values. RapidJSON only defines these operations for object types; invoking them on a non-object violates the class invariant and results in undefined behavior (out-of-bounds read), commonly crashing the process. Affected Scenarios: An operator-configured (or compromised) Discovery backend returns a malformed /discovery/nodes or /discovery/fetchs response whose data/service/instance entries are not JSON objects, crashing any bRPC client that refreshes its server list. How to Fix: 1. Upgrade bRPC to version 1.18.0 or later, which fixes this issue. 2. Apply this patch: https://github.com/apache/brpc/pull/3533 The fix validates that the Discovery response data, per-service data, and instance entries are JSON objects (and skips non-object node/instance entries and rejects non-object data/service values) before calling member accessors.
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-87849?
How severe is CVE-2026-87849?
How do I fix CVE-2026-87849?
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-87841The UnitechPay WordPress plugin through 1.0.6.3 does not ve…5.3
- CVE-2026-87842The Zonify WordPress plugin before 1.0.5 does not perform a…7.5
- CVE-2026-87843The Trust Payments Gateway for WooCommerce WordPress plugin …6.5
- CVE-2026-87844The PickPlugins Product Designer for WooCommerce WordPress p…5.3
- CVE-2026-87846The Shipping for Nova Poshta WordPress plugin through 1.19.8…5.3
- CVE-2026-87848The MPCX Lightbox WordPress plugin 1.2.2 through 1.2.5 does …3.7
- CVE-2026-8785A flaw has been found in projectworlds hospital-management-s…7.3
- CVE-2026-87853A flaw was found in SSSD's IdP authentication provider. The …7.5
- CVE-2026-87854The Subscriptions for WooCommerce WordPress plugin before 2.…5.3
- CVE-2026-87855The JTL-Connector for WooCommerce plugin for WordPress is vu…9.8
- CVE-2026-87858Temporal Server decided whether a Workflow completion callba…7.2
- CVE-2026-87859morgan is an HTTP request logger middleware for Node.js. In …5.3
Are you affected by CVE-2026-87849?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
