CVSS 4.0
9.3 criticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NCritical (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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:Ngithub.com/openflagr/flagr (Go): fixed in 0.0.0-20251009103504-fe83dc87aa40Explain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| OpenFlagr Flagr | through 1.1.18 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-rwp9-5g7q-73q3 | Go | github.com/openflagr/flagr | <0.0.0-20251009103504-fe83dc87aa40 | 0.0.0-20251009103504-fe83dc87aa40 |
| GO-2026-4286 | Go | github.com/openflagr/flagr | <0.0.0-20251009103504-fe83dc87aa40 | 0.0.0-20251009103504-fe83dc87aa40 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| openSUSE | Leap 15.6 | govulncheck-vulndb | 0.0.20260114T191543-150000.1.137.1 | SUSE-SU-2026:0142-1 |
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 | openSUSE-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.
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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.