What is CVE-2026-0650?

CVE-2026-0650 is a critical-severity missing authentication for critical function vulnerability in github.com/openflagr/flagr (go), affecting versions < 0.0.0-20251009103504-fe83dc87aa40. It is fixed in 0.0.0-20251009103504-fe83dc87aa40. A critical operation is accessible without requiring any authentication.

Which versions of github.com/openflagr/flagr are affected by CVE-2026-0650?

github.com/openflagr/flagr (go) versions < 0.0.0-20251009103504-fe83dc87aa40 is affected.

Is there a fix for CVE-2026-0650?

Yes. CVE-2026-0650 is fixed in 0.0.0-20251009103504-fe83dc87aa40. Upgrade to this version or later.

Is CVE-2026-0650 exploitable, and should I be worried?

Whether CVE-2026-0650 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-0650 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-0650 in github.com/openflagr/flagr

Q: Which versions of github.com/openflagr/flagr are affected by CVE-2026-0650?

github.com/openflagr/flagr (go) versions < 0.0.0-20251009103504-fe83dc87aa40 is affected.

Q: Is there a fix for CVE-2026-0650?

Yes. CVE-2026-0650 is fixed in 0.0.0-20251009103504-fe83dc87aa40. Upgrade to this version or later.

Q: Is CVE-2026-0650 exploitable, and should I be worried?

Whether CVE-2026-0650 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-0650 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-0650?

Upgrade github.com/openflagr/flagr to 0.0.0-20251009103504-fe83dc87aa40 or later.

Summary

OpenFlagr contains an authentication bypass vulnerability in the HTTP middleware

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.

Impact

A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.

Affected versions

github.com/openflagr/flagr (< 0.0.0-20251009103504-fe83dc87aa40)

Security releases

github.com/openflagr/flagr → 0.0.0-20251009103504-fe83dc87aa40 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade github.com/openflagr/flagr to 0.0.0-20251009103504-fe83dc87aa40 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-0650? CVE-2026-0650 is a critical-severity missing authentication for critical function vulnerability in github.com/openflagr/flagr (go), affecting versions < 0.0.0-20251009103504-fe83dc87aa40. It is fixed in 0.0.0-20251009103504-fe83dc87aa40. A critical operation is accessible without requiring any authentication.
Which versions of github.com/openflagr/flagr are affected by CVE-2026-0650? github.com/openflagr/flagr (go) versions < 0.0.0-20251009103504-fe83dc87aa40 is affected.
Is there a fix for CVE-2026-0650? Yes. CVE-2026-0650 is fixed in 0.0.0-20251009103504-fe83dc87aa40. Upgrade to this version or later.
Is CVE-2026-0650 exploitable, and should I be worried? Whether CVE-2026-0650 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-0650 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-0650? Upgrade github.com/openflagr/flagr to 0.0.0-20251009103504-fe83dc87aa40 or later.