CVE Hunter
›
CVE-2026-84747

CWE-436

HIGH CVSS 7.5 NVD

Interpretation conflict in the HTTP protocol implementation in Apache bRPC (version < 1.18.0) on all platforms allows remote attackers to bypass access control rules enforced by a front proxy. Root Cause: The method dispatch function FindMethodPropertyByURI() in bRPC's HTTP protocol splits the request path with a string splitter that skips empty fields, so paths containing empty path segments (consecutive slashes), such as //flags, /flags// and /flags//port, are dispatched to the same method as their collapsed form /flags. Per RFC 3986 these are distinct paths. A front proxy that enforces an ACL (e.g. blocking access to builtin services such as /flags) matches the collapsed form only, and therefore forwards the padded literal to the bRPC server, where it is dispatched as if it were the collapsed form. This differential allows //flags?setvalue= to reach a builtin service that /flags is not allowed to reach. Additionally, the HTTP/2 implementation never validated the :path pseudo-header, so requests without a :path, or with a :path that neither begins with '/' nor is the asterisk-form '*', contrary to RFC 9113 section 8.3.1, were not rejected. Affected Scenarios: Deployments of Apache bRPC behind a front proxy or gateway that performs access control (ACL) decisions on the literal request path, where the bRPC server accepts HTTP or HTTP/2 traffic from that proxy. In such deployments an attacker can send a path containing empty path segments to reach a resource that the front proxy intended to block. 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/3512 Note: After applying the fix, HTTP and HTTP/2 request paths containing empty path segments (consecutive slashes) are rejected by default, and HTTP/2 :path values that are empty or neither begin with '/' nor equal '*' are rejected. Deployments that depend on the previous lenient behavior can restore it by turning on the gflag -http_allow_empty_path_segments, which is not recommended for servers exposed to untrusted traffic.

Yayınlanma 21.10.2026
ISO Tarih 2026-10-21
CVSS Sürüm v3.1
Kaynak NVD
CVSS v3.1 Metrikleri
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Attack Vector Network AV:N
Attack Complexity Low AC:L
Privileges Req. None PR:N
User Interaction None UI:N
Scope Unchanged S:U
Confidentiality None C:N
Integrity High I:H
Availability None A:N
AI Güvenlik Analizi
🤖 Yapay Zeka Güvenlik Analizi Hazırlanıyor…
CVSS vektörü ve CWE zayıflık yapısı inceleniyor…
Hedef Keşif Sorguları
CVSS Skoru
7.5 / 10 · CVSS HIGH
Zayıflık Türleri (CWE)
CWE-436
Referanslar (1)
İlgili CVE'ler
6.5
CVE-2026-128071
### Summary Nuxt matches route rules against the request path with encoded slashes (`%2F`) left encoded, whil
6.5
CVE-2026-129299
### Impact Two effects, sharing the root cause of Advisory 1 — header names chosen by the sender were resol
6.5
CVE-2026-129301
### Impact `write_attachments()` called `_safe_attachment_filename()` and `write_sample()` inside its loop wi
6.5
CVE-2026-128077
### Summary Since `4.6.0`, Nuxt parses a request path that starts with `//` as a URL with a host before rende
5.3
CVE-2026-126210
### Summary `@hono/node-server` passes the raw request-target to the WHATWG URL parser, which treats a backsl
4.8
CVE-2026-126354
### Summary `Addressable::URI.normalize_path` resolves some paths containing `..` segments to a different pat