OpenFlagr Flagr
OpenFlagr <= 1.1.18 Authentication Bypass via Prefix Whitelist Path Normalization
OpenFlagr versions prior to and including 1.1.18 contain an authentication bypass vulnerability in the HTTP middleware. Due to improper handling of path normalization in the whitelist logic, crafted requests can bypass authentication and access protected API endpoints without valid credentials. Unauthorized access may allow modification of feature flags and export of sensitive data.
Affected versions and mitigation
From the CVE record, GitHub Security Advisories and the vendor's references.Affected
- <= 1.1.18
- < 0.0.0-20251009103504-fe83dc87aa40
Fixed in 0.0.0-20251009103504-fe83dc87aa40
from GitHub Security Advisory GHSA-rwp9-5g7q-73q3
Mitigation
Upgrade github.com/openflagr/flagr to 0.0.0-20251009103504-fe83dc87aa40 or later.
References
Timeline
Days relative to CVE publicationFirst public PoC 243 days after publication; not in CISA KEV. First PoC: nuclei template: OpenFlagr <= 1.1.18 - Authentication Bypass (nuclei template, 6 Sep 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| CVE record (tagged exploit) | https://dreyand.rs/code%20review/golang/2026/01/03/0day-speedrun-openflagr-less-1118-authentication-bypass | unknown | 14 Nov 2026 |
| nuclei template | nuclei template: OpenFlagr <= 1.1.18 - Authentication Bypass | 6 Sep 2026 | 14 Nov 2026 |