frp is a fast reverse proxy. From 0.43.0 to 0.68.0, frp contains an authentication bypass in the HTTP vhost routing path when routeByHTTPUser is used as part of access control. In proxy-style requests, the routing logic uses the username from Proxy-Authorization to select the routeByHTTPUser backend, while the access control check uses credentials from the regular Authorization header. As a result, an attacker who can reach the HTTP vhost entrypoint and knows or can guess the protected routeByHTTPUser value may access a backend protected by httpUser / httpPassword even with an incorrect Proxy-Authorization password. This issue affects deployments that explicitly use routeByHTTPUser. It does not affect ordinary HTTP proxies that do not use this feature. This vulnerability is fixed in 0.68.1.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/fatedier/frp/security/advisories/GHSA-pq96-pwvg-vrr9 Exploit, Vendor Advisory
- https://github.com/fatedier/frp/security/advisories/GHSA-pq96-pwvg-vrr9 Exploit, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 9.1 · fatedierNVD modified 2026-10-26 21:10
Affected (CPE criteria) 1
cpe:2.3:a:fatedier:frp:*:*:*:*:*:*:*:*
References 2
- https://github.com/fatedier/frp/security/advisories/GHSA-pq96-pwvg-vrr9 Exploit, Vendor Advisory
- https://github.com/fatedier/frp/security/advisories/GHSA-pq96-pwvg-vrr9 Exploit, Vendor Advisory