CVE-2026-61739

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-114005 (ENISA EUVD)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. Prior to 0.1.77, the Velociraptor Sigma exclusion-management endpoints in backend/app/incidents/routes/incident_alert.py omit role and tenant authorization, and POST /api/incidents/alerts/create/velo-sigma/exclusion does not validate credentials. Its return_username_for_logging dependency in backend/app/auth/utils.py calls decode_token, which returns ordinary Invalid token or Expired signature strings on failure, and the dependency passes these strings through instead of rejecting the request. A Bearer header is required, but an arbitrary invalid, expired or forged value can create a suppression rule without a valid account. The collection GET at /create/velo-sigma/exclusion lists exclusions; the read, update and delete routes under /create/velo-sigma/exclusion/{exclusion_id}, and the /velo-sigma/exclusion/{exclusion_id}/toggle route, use get_current_user without role checks, permitting any authenticated customer_user to manage every exclusion. In backend/app/incidents/services/velo_sigma.py, process_sigma_alert calls check_exclusions and drops matching enabled alerts before incident creation. A null customer_code applies a rule across all tenants. Attackers can suppress detections platform-wide through channel, title or field matching, while low-privilege accounts can enumerate detection-tuning data and modify, disable or delete legitimate exclusions. This issue is fixed in version 0.1.77.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 30, 2026

Last Modified

October 30, 2026

Advisory Details (4)

Auto-updated Oct 30, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit.
Web page

GitHub - socfortress/CoPilot at v0.1.77 · GitHub

https://github.com/socfortress/CoPilot/tree/v0.1.77
GitHub commit Patch Available

commit d22f80f9086e (socfortress/CoPilot)

Patch available: socfortress/CoPilot v0.1.77 (contains commit d22f80f9086e)

https://github.com/socfortress/CoPilot/commit/d22f80f9086ef5e68baa3a9414bff7d7621a14a8
GitHub pull request Patch Available

fix(security): require admin/analyst on Velociraptor Sigma exclusion routes (GHSA-c6jc-rh4j-wg88)

Patch available: socfortress/CoPilot v0.1.77 (PR #942 merged 2026-06-24)

https://github.com/socfortress/CoPilot/pull/942
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Authentication Bypass and Missing Authorization on Velociraptor Sigma Exclusion Rules (Detection Suppression) · Advisory · socfortress/CoPilot · GitHub

https://github.com/socfortress/CoPilot/security/advisories/GHSA-c6jc-rh4j-wg88

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 15× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-11-10 18:13 UTCEchelonGraph re-scored
  4. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-11-03 18:31 UTCEchelonGraph re-scored
  12. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  16. 2026-10-30 16:02 UTCENISA EUVD ID recordedEUVD-2026-114005 · Source: ENISA EUVD
  17. 2026-10-30 15:26 UTCEchelonGraph re-scored
  18. 2026-10-30 14:55 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  19. 2026-10-30 14:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61739?
CVE-2026-61739 is a high-severity vulnerability; its CVE record was published on October 30, 2026. SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. Prior to 0.1.77, the Velociraptor Sigma exclusion-management endpoints in backend/app/incidents/routes/incident_alert.py omit role and tenant authorization, and POST…
When was the CVE record for CVE-2026-61739 published?
The CVE record for CVE-2026-61739 was published on October 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-61739 actively exploited?
CVE-2026-61739 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61739?
CVE-2026-61739 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61739?
A fix for CVE-2026-61739 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-61739

Explore →

Is Your Infrastructure Affected by CVE-2026-61739?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs