OpenFlagr contains an authentication bypass vulnerability in the HTTP middleware in github.com/openflagr/flagr

The authentication bypass vulnerability in OpenFlagr presents a severe risk. An attacker who successfully exploits this flaw can bypass authentication checks and gain unauthorized access to the entire OpenFlagr system. This could allow them to modify feature flag configurations, potentially disrupting application functionality or exposing sensitive data. The impact extends beyond simple data access; an attacker could manipulate the application's behavior in unpredictable ways, leading to denial of service or even complete compromise of the underlying infrastructure. Given the critical nature of feature flag management in modern applications, this vulnerability could have a wide-ranging and devastating impact.

Organizations utilizing OpenFlagr for feature flag management, particularly those with critical applications relying on feature flags for functionality or security, are at significant risk. This includes teams deploying OpenFlagr in production environments, especially those with limited security controls or legacy configurations. Shared hosting environments where OpenFlagr instances are deployed alongside other applications are also at increased risk.

• go / server: Use go build to compile the OpenFlagr source code and analyze the HTTP middleware in github.com/openflagr/flagr for missing authentication checks. • go / server: Examine OpenFlagr logs for unusual patterns of requests or authentication failures. • generic web: Monitor access logs for requests to OpenFlagr endpoints without proper authentication headers. • generic web: Use curl -v <OpenFlagr_endpoint> to test authentication bypass attempts.

1. 2026-01-12Disclosure

   disclosure

1. Reserviert2026-01-06
2. Veröffentlicht2026-01-12
3. Geändert2026-03-03
4. EPSS aktualisiert2026-03-23

The primary mitigation for CVE-2026-0650 is to immediately upgrade OpenFlagr to version 0.0.0-20251009103504-fe83dc87aa40 or later. If upgrading is not immediately feasible, consider implementing temporary workarounds such as restricting access to the OpenFlagr API to trusted networks or users. Review and strengthen authentication policies for all users accessing the OpenFlagr system. Monitor OpenFlagr logs for any suspicious activity, particularly attempts to access resources without proper authentication. While a WAF cannot directly prevent this bypass, it can help detect and block malicious requests attempting to exploit the vulnerability.