Advisory [CVE-2026-86249] On a brpc::Server that sets both ServerOptions.auth and ServerOptions.internal_port, the HTTP built-in service exemption on internal_port can be abused to bypass authentication entirely
This security Apache Software Foundation advisory covers CVE-2026-86249; 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
On a brpc::Server that sets both ServerOptions.auth and ServerOptions.internal_port, the HTTP built-in service exemption on internal_port can be abused to bypass authentication entirely.
VerifyHttpRequest() returns true without checking any credential when a built-in service is requested on internal_port, and this verdict is not per - request: verification runs only for the first message of a connection and the result latches the connection.
Sending a request such as GET /status to internal_port first authenticates the whole connection, after which every subsequent request dispatched on the same connection is handled without ever calling VerifyHttpRequest().
This lets a remote attacker reach ordinary (non-built-in, non-tabbed) authenticated services without supplying valid credentials whenever the server uses ServerOptions.internal_port together with an Authenticator.
The fix restricts internal_port so that it carries only built-in and Tabbed services; requests for ordinary services sent to internal_port are rejected with EPREM / HTTP 403.
Mitigation / Fix: upgrade to 1.18.0 or apply PR.
Users who rely on serving normal services on internal_port must move those requests to the port passed to Server::Start().
Affected product named by the advisory: Apache bRPC.
- Apache bRPC before 1.18.0
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
- Mitigation / Fix: upgrade to 1.18.0 or apply PR https://github.com/apache/brpc/pull/3525.
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-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-84748Oct 21, 2026Improper authorization in Apache bRPC (versions < 1.18.0) on all platforms allows remote
- 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.