Advisory [CVE-2026-84748] Improper authorization in Apache bRPC (versions < 1.18.0) on all platforms allows remote attackers to access builtin services through the public port
This security Apache Software Foundation advisory covers CVE-2026-84748; related products: Apache bRPC.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Get an email when Apache Software Foundation publishes the next one.
VulniPulse checks Apache Software Foundation's security advisories around the clock and emails you new ones with the severity, the fixed version and the vendor's link. First month free, then US$15/month; we email you before the first charge.
Summary
Improper authorization in Apache bRPC (versions < 1.18.0) on all platforms allows remote attackers to access builtin services through the public port.
Root Cause: ServerOptions.internal_port is documented to make builtin services (and Tabbed services) reachable only from the internal port, and the HTTP/h2 dispatch path enforced this.
However, all protobuf-based protocol dispatch paths (baidu_std, hulu_pbrpc, sofa_pbrpc, and the nshead-based protocols public_pbrpc, nshead_mcpack, nova_pbrpc and ubrpc2pb) computed the security_mode flag but never enforced it between method resolution and method invocation.
Since builtin services share the method map with user services, a client able to reach the public port could invoke builtin services such as brpc.vars or hotspots by name over these pb protocols and disclose sensitive runtime information (metrics, flags, profiler data) that the operator intended to expose only via the internal port.
Affected Scenarios: Use a bRPC server with ServerOptions.internal_port configured (or with builtin/Tabbed services otherwise expected to be gated by it) while the public port is reachable from an untrusted network and any pb-based protocol is enabled.
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:
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.
Official advisory · medium-confidence parse· fetched 7 days ago·verify at source
- 1.18.0
Official advisory · medium-confidence parse· fetched 7 days ago·verify at source
Mitigation checklist
- Upgrade bRPC to version 1.18.0, which fixes this issue.
- Apply this patch: https://github.com/apache/brpc/pull/3511
Official advisory · medium-confidence parse· fetched 7 days ago·verify at source
More Apache Software Foundation advisories
- CVE-2026-90484Oct 21, 2026The MySQL client response parser in Apache bRPC dereferences a null pointer
- CVE-2026-87849Oct 21, 2026The Discovery naming-service reply parser in Apache bRPC (versions < 1.18.0) calls
- CVE-2026-86249Oct 21, 2026On a brpc::Server that sets both ServerOptions.auth and ServerOptions.internal_port
- CVE-2026-86147Oct 21, 2026External control of file name or path and uncontrolled resource consumption in Apache bRPC
- CVE-2026-86146Oct 21, 2026Inconsistent interpretation of HTTP requests (HTTP request/response smuggling)
- CVE-2026-84747Oct 21, 2026Interpretation conflict in the HTTP protocol implementation in Apache bRPC
Android app · Google Play
Monitor future Apache Software Foundation CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.