cve.bz

CVE-2026-0650 openflagr flagr: Forced Browsing

9.3 criticalEPSS 1.5%Fix available

Critical (9.3) in openflagr flagr. EPSS 1.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/openflagr/flagr 0.0.0-20251009103504-fe83dc87aa40.

On this page
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.

Severity

CVSS 4.0

9.3 critical
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
EPSS
1.5% (unchanged from 1.5% a week ago; 1.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 75th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: total, assessed 2026-01-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-306 Missing Authentication for Critical Functionality
CWE-425 Direct Request (Forced Browsing)
OWASP Top 10
A01:2025 Broken Access Control, A07:2025 Authentication Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-0650 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-0650?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-0650?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-0650 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
OpenFlagr Flagrthrough 1.1.18

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rwp9-5g7q-73q3Gogithub.com/openflagr/flagr<0.0.0-20251009103504-fe83dc87aa400.0.0-20251009103504-fe83dc87aa40
GO-2026-4286Gogithub.com/openflagr/flagr<0.0.0-20251009103504-fe83dc87aa400.0.0-20251009103504-fe83dc87aa40

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 15.6govulncheck-vulndb0.0.20260114T191543-150000.1.137.1SUSE-SU-2026:0142-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-36 Using Unpublished Interfaces or Functionality Likelihood: Medium · Severity: High
  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-166 Force the System to Reset Values Severity: Medium
  • CAPEC-216 Communication Channel Manipulation
  • CAPEC-87 Forceful Browsing Likelihood: High · Severity: High
  • CAPEC-127 Directory Indexing Likelihood: High · Severity: Medium
  • CAPEC-143 Detect Unpublicized Web Pages Severity: Low
  • CAPEC-144 Detect Unpublicized Web Services Severity: Low
  • CAPEC-668 Key Negotiation of Bluetooth Attack (KNOB) Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON