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

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

- **Identifiers:** `GHSA-rwp9-5g7q-73q3` · `CVE-2026-0650` · `GO-2026-4286`
- **State:** Confirmed
- **Severity:** CVSS 9.3 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-306](https://cwe.mitre.org/data/definitions/306.html) · [CWE-425](https://cwe.mitre.org/data/definitions/425.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 12 Jan 2026
- **Updated:** 3 Mar 2026
- **Reviewed by a person:** No

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.

## Critical

Critical, because:

- CVSS score 9.3: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `github.com/openflagr/flagr` (Go): affected `<0.0.0-20251009103504-fe83dc87aa40`; fixed in `0.0.0-20251009103504-fe83dc87aa40`

## 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

- 9.3 Critical, CVSS 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`, from 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

- 7 Jan 2026, 04:29 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-0650)

## Sources

- [GitHub Advisory Database: GHSA-rwp9-5g7q-73q3](https://github.com/advisories/GHSA-rwp9-5g7q-73q3)
- [OSV: GHSA-rwp9-5g7q-73q3](https://osv.dev/vulnerability/GHSA-rwp9-5g7q-73q3)
- <https://github.com/advisories/GHSA-rwp9-5g7q-73q3>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-0650>
- <https://github.com/openflagr/flagr/commit/fe83dc87aa404a57554aa5839ac450f55c203570>
- <https://dreyand.rs/code%20review/golang/2026/01/03/0day-speedrun-openflagr-less-1118-authentication-bypass>
- <https://github.com/openflagr/flagr/releases/tag/1.1.19>
- <https://www.vulncheck.com/advisories/openflagr-authentication-bypass-via-prefix-whitelist-path-normalization>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-rwp9-5g7q-73q3>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-rwp9-5g7q-73q3/>. Everything for agents: <https://agentprime.io/llms.txt>.
