Which products and versions are affected by CVE-2026-0650?

Affected: github.com/openflagr/flagr (go); Flagr. The full list is in the CVE brief.

Is CVE-2026-0650 being exploited in the wild?

It is not listed in any known-exploited vulnerabilities catalog.

Is CVE-2026-0650 in the CISA KEV catalog?

No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

Is there a public exploit for CVE-2026-0650?

Public exploit code is available.

Is there a fix for CVE-2026-0650?

Fixed versions are available, including github.com/openflagr/flagr 0.0.0-20251009103504-fe83dc87aa40.

How urgently should CVE-2026-0650 be patched?

Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.

Request A Demo

Vulnerability Intelligence

CVE-2026-0650

CriticalPublic exploit

OpenFlagr contains an authentication bypass vulnerability in the HTTP middleware

Published Jan 7, 2026 · Updated Oct 10, 2026 · Also known as GHSA-rwp9-5g7q-73q3, GO-2026-4286

Key Facts

Patch immediately

CVE-2026-0650 is a critical-severity vulnerability (CVSS 9.3 v4) affecting github.com/openflagr/flagr (go), Flagr.
It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
EPSS estimates a 1.5% probability of exploitation in the next 30 days.
Fixed versions are available, including github.com/openflagr/flagr 0.0.0-20251009103504-fe83dc87aa40.
Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.

CVSS v4

9.3

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

EPSS (30-day exploit likelihood)

1.5%

Higher than 74.1% of all scored CVEs

Exploited in the wild

No known

Not in a known-exploited catalog

Public exploit code

Available

Proof-of-concept or weaponized module

Get the full CVE-2026-0650 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

Description

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 Products

2 affected entries in total

Product	Affected versions	Fixed in
github.com/openflagr/flagrgo	See advisory	0.0.0-20251009103504-fe83dc87aa40
Flagr	See advisory	n/a

Patched Releases

github.com/openflagr/flagr

0.0.0-20251009103504-fe83dc87aa40

Timeline

Publicly disclosed
Jan 7, 2026
Last updated
Oct 10, 2026

Weakness Type

CWE-306 Missing Authentication for Critical Function
CWE-425 Direct Request ('Forced Browsing')

References

2 more references in the full CVE brief

FAQ

Common Questions.

OpenFlagr versions prior to and including 1.1.18 contain an authentication bypass vulnerability in the HTTP middleware.
Affected: github.com/openflagr/flagr (go); Flagr. The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
Public exploit code is available.
Fixed versions are available, including github.com/openflagr/flagr 0.0.0-20251009103504-fe83dc87aa40.
Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.

Is CVE-2026-0650 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.