How severe is GHSA-rwp9-5g7q-73q3?

No CVSS score has been assigned to GHSA-rwp9-5g7q-73q3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rwp9-5g7q-73q3?

GHSA-rwp9-5g7q-73q3 affects the following packages: github.com/openflagr/flagr (Go). Ecosystems affected: Go.

How do I fix GHSA-rwp9-5g7q-73q3?

Update github.com/openflagr/flagr to 0.0.0-20251009103504-fe83dc87aa40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rwp9-5g7q-73q3 is resolved across your whole dependency graph.

How do I detect GHSA-rwp9-5g7q-73q3 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openflagr/flagr. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-rwp9-5g7q-73q3 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-rwp9-5g7q-73q3?

O3 pinpoints whether GHSA-rwp9-5g7q-73q3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-rwp9-5g7q-73q3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-rwp9-5g7q-73q3 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-rwp9-5g7q-73q3?

GHSA-rwp9-5g7q-73q3 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-rwp9-5g7q-73q3?

GHSA-rwp9-5g7q-73q3 is classified as Missing Authentication (CWE-306), CWE-425 (CWE-425). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-rwp9-5g7q-73q3 published, and has it been updated?

GHSA-rwp9-5g7q-73q3 was published on January 7, 2026 and was last updated on February 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-rwp9-5g7q-73q3: flagr Authentication Bypass

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk35th percentile+0.28%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐹github.com/openflagr/flagr

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

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 Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/openflagr/flagr`	all versions	0.0.0-20251009103504-fe83dc87aa40

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openflagr/flagr. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/openflagr/flagr to 0.0.0-20251009103504-fe83dc87aa40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rwp9-5g7q-73q3 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-rwp9-5g7q-73q3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-rwp9-5g7q-73q3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-rwp9-5g7q-73q3 in your dependencies?

O3 detects GHSA-rwp9-5g7q-73q3 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-rwp9-5g7q-73q3