Live › vulnerability › CVE-2026-84748
Go to dashboardApache bRPC versions before 1.18.0 fail to enforce the internal_port restriction on protobuf-based protocols, so builtin services can be invoked through the public port. An attacker who can reach that port can read runtime metrics, flags and profiler data the operator meant to keep internal.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Servers that set ServerOptions.internal_port (or rely on builtin/Tabbed services being gated by it) while the public port faces an untrusted network and a protobuf-based protocol is enabled. Servers that do not expose the public port to untrusted clients, or that run no internal_port gating, have less exposure.
No product ranges from the sources yet.
1.18.0.ServerOptions.internal_port being set in the server code, and confirm whether the public port is reachable from untrusted networks.1.18.0.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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)
This page as .md · .json · in your agent: get_signal("CVE-2026-84748")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.