Advisory record · GHSA-rwp9-5g7q-73q3

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

CVSS 9.3 CriticalCriticalEPSS 0.015 · 75th percentile

Critical, because:

  • CVSS score 9.3: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 12 Jan 2026, 17:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/openflagr/flagrGo<0.0.0-20251009103504-fe83dc87aa400.0.0-20251009103504-fe83dc87aa40
Identifiers
GHSA-rwp9-5g7q-73q3 · CVE-2026-0650 · GO-2026-4286
Weakness (CWE)
CWE-306 · CWE-425
Published
12 Jan 2026
Updated
3 Mar 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

OpenFlagr (github.com/openflagr/flagr) versions before 0.0.0-20251009103504-fe83dc87aa40 contain an authentication bypass in the HTTP middleware. The source gives few details on how the bypass works or what an attacker can access. Upgrade to 0.0.0-20251009103504-fe83dc87aa40 or later.

Written 10 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.3 Critical 4.0 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 CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.015, the 75th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 7 Jan 2026, 04:29 UTC Confirmed by the CVE List

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.