SocFortress CoPilot up to 0.1.75 Webhook Verification graylog.py verify_graylog_header/verify_velociraptor_header COMMAND/ACTION/VALUE/AGENT_ID improper authentication

Summaryinfo

A vulnerability was found in SocFortress CoPilot up to 0.1.75. It has been rated as critical. The affected element is the function verify_graylog_header/verify_velociraptor_header of the file backend/app/active_response/routes/graylog.py of the component Webhook Verification. The manipulation of the argument COMMAND/ACTION/VALUE/AGENT_ID leads to improper authentication. This vulnerability is traded as CVE-2026-61729. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as critical, has been found in SocFortress CoPilot up to 0.1.75. This issue affects the function verify_graylog_header/verify_velociraptor_header of the file backend/app/active_response/routes/graylog.py of the component Webhook Verification. The manipulation of the argument COMMAND/ACTION/VALUE/AGENT_ID with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

SOCFortress CoPilot focuses on providing a single pane of glass for all your security operations needs. Prior to 0.1.76, `verify_graylog_header` in `backend/app/active_response/routes/graylog.py` and `verify_velociraptor_header` in `backend/app/incidents/routes/incident_alert.py` authenticate webhooks against `GRAYLOG_API_HEADER_VALUE` and `VELOCIRAPTOR_API_HEADER_VALUE` with the same publicly hardcoded fallback. The same default is shipped in `.env.example`. Deployments that leave either setting unset or unchanged permit an anonymous caller with the known header value to bypass the JWT authentication required by normal APIs. `POST /api/graylog/invoke` forwards attacker-selected `COMMAND`, `ACTION`, `VALUE` and `AGENT_ID` to the configured Wazuh manager without the command-enum validation of the authenticated invocation route, allowing active-response scripts to disrupt endpoints and manipulate defensive controls. `POST /api/incidents/alerts/create/threshold` and `POST /api/incidents/alerts/create/velo-sigma` accept forged alerts for arbitrary `customer_code` values and drive attacker-controlled OpenSearch queries. Active-response delivery requires a configured reachable Wazuh manager. Deployments with independently changed header secrets are not subject to this default-secret bypass. This issue is fixed in version 0.1.76.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-61729 since 07/10/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.

Upgrading to version 0.1.76 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider 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

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 the best quality for vulnerability data then you always have to consider VulDB.

Discussion