CVE-2026-130860
8.2HighPublished 17 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
High
0CVSS v3.110
- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User action
- None
- Impact
- High impact on integrity
- Weakness
- CWE-1188
What an attacker gets
Unauthenticated attackers can modify, delete, or create feature flags by accessing the API without credentials. This occurs because the default whitelist configuration incorrectly exposes sensitive endpoints.
Root cause
The basicAuth.whitelist middleware uses prefix matching that ignores HTTP methods, allowing unauthorized access to restricted API routes.
Affected versions
Flagr versions before 1.2.5
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
Fix & remediation
Upgrade to Flagr 1.2.5 or later. If you cannot upgrade immediately, manually update the FLAGR_BASIC_AUTH_WHITELIST_PATHS environment variable to remove /api/v1/flags and any other sensitive paths from the whitelist.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
Flagr before 1.2.5 contains an authentication bypass vulnerability that allows unauthenticated remote attackers to access the flag management write API through an insecure default FLAGR_BASIC_AUTH_WHITELIST_PATHS including /api/v1/flags. Because basicAuth.whitelist() in pkg/config/middleware.go matches only path prefixes regardless of HTTP method, attackers can create, modify, enable, disable, and delete flags, variants, segments, constraints, and distributions.
References
- https://github.com/openflagr/flagr/blob/1.2.4/pkg/config/env.go#L256
- https://github.com/openflagr/flagr/blob/1.2.4/pkg/config/middleware.go#L250-L262
- https://github.com/openflagr/flagr/commit/c7e995e3fa2d4d084cf1e722859aa00921626d53
- https://github.com/openflagr/flagr/issues/813
- https://github.com/openflagr/flagr/releases/tag/1.2.5
- https://www.vulncheck.com/advisories/flagr-before-1.2.5-authentication-bypass-via-default-basic-auth-whitelist