CVE-2026-0650
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenFlagr 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceOpenFlagr versions up to 1.1.18 have an authentication bypass vulnerability in the HTTP middleware due to improper path normalization handling in the whitelist logic. Attackers can craft malicious requests that bypass authentication and access protected API endpoints to modify feature flags or exfiltrate sensitive data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OpenFlagr versionCheck the running container or installed binary version using 'flagr --version' or inspect the container image metadata. Alternatively, query the /health or /version API endpoint if accessible.Affected if The installed version is 1.1.18 or lower.
-
Verify authentication middleware is enabledInspect the OpenFlagr configuration file (typically config.yaml or config.json) or environment variables for 'AUTH_*' settings such as AUTH_ENABLED, AUTH_TYPE, or similar authentication-related flags.Affected if Authentication is enabled in the configuration (AUTH_ENABLED=true or similar).
-
Check for public network exposureReview network configuration, firewall rules, or container/network orchestration settings to determine if the OpenFlagr API ports (typically 8080 or 443) are exposed to untrusted networks or the public internet.Affected if The OpenFlagr API is reachable from untrusted network segments or the public internet.
-
Examine whitelist path configurationReview the OpenFlagr configuration for any whitelist or bypass rules related to API path handling. Look for settings involving 'WHITELIST', 'PUBLIC_PATHS', or path matching configurations.Affected if Whitelist or path exemption rules are configured that could be vulnerable to path normalization bypass.
A user is affected if they are running OpenFlagr version 1.1.18 or lower with authentication enabled and the API is network-accessible to potential attackers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade OpenFlagr to a version newer than 1.1.18 which contains the patch for the path normalization vulnerability in the authentication whitelist logic.
OpenFlagr version 1.1.19 or later
- 1. Identify the currently running OpenFlagr version using `flagr version` or checking your container/deployment configuration
- 2. If the current version is 1.1.18 or earlier, plan for an upgrade to a fixed release
- 3. Before upgrading in production, test the new version in a staging environment to verify functionality
- 4. Back up any existing feature flag configurations and data
- 5. Perform the upgrade by pulling the new container image or installing the updated package
- 6. Verify that authentication is now properly enforced by attempting to access protected endpoints without credentials (these requests should be rejected)
- 7. Confirm normal authentication flows still work with valid credentials
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0650 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0650 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data