SOCFortress CoPilot up to 0.1.76 Sigma Exclusion Management utils.py decode_token improper authorization

Summaryinfo

A vulnerability was found in SOCFortress CoPilot up to 0.1.76. It has been declared as critical. This affects the function decode_token of the file backend/app/auth/utils.py of the component Sigma Exclusion Management. The manipulation results in improper authorization. This vulnerability is reported as CVE-2026-61739. The attack can be launched remotely. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in SOCFortress CoPilot up to 0.1.76. It has been classified as critical. Affected is the function decode_token of the file backend/app/auth/utils.py of the component Sigma Exclusion Management. The manipulation with an unknown input leads to a improper authorization vulnerability. CWE is classifying the issue as CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is available at github.com. This vulnerability is traded as CVE-2026-61739 since 07/10/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1548.002 by the MITRE ATT&CK project.

Upgrading to version 0.1.77 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• SOCFortress

Name

• CoPilot

Version

• 0.1.0
• 0.1.1
• 0.1.2
• 0.1.3
• 0.1.4
• 0.1.5
• 0.1.6
• 0.1.7
• 0.1.8
• 0.1.9
• 0.1.10
• 0.1.11
• 0.1.12
• 0.1.13
• 0.1.14
• 0.1.15
• 0.1.16
• 0.1.17
• 0.1.18
• 0.1.19
• 0.1.20
• 0.1.21
• 0.1.22
• 0.1.23
• 0.1.24
• 0.1.25
• 0.1.26
• 0.1.27
• 0.1.28
• 0.1.29
• 0.1.30
• 0.1.31
• 0.1.32
• 0.1.33
• 0.1.34
• 0.1.35
• 0.1.36
• 0.1.37
• 0.1.38
• 0.1.39
• 0.1.40
• 0.1.41
• 0.1.42
• 0.1.43
• 0.1.44
• 0.1.45
• 0.1.46
• 0.1.47
• 0.1.48
• 0.1.49
• 0.1.50
• 0.1.51
• 0.1.52
• 0.1.53
• 0.1.54
• 0.1.55
• 0.1.56
• 0.1.57
• 0.1.58
• 0.1.59
• 0.1.60
• 0.1.61
• 0.1.62
• 0.1.63
• 0.1.64
• 0.1.65
• 0.1.66
• 0.1.67
• 0.1.68
• 0.1.69
• 0.1.70
• 0.1.71
• 0.1.72
• 0.1.73
• 0.1.74
• 0.1.75
• 0.1.76

Website

• Product: https://github.com/socfortress/CoPilot/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion