---
id: "CVE-2026-61729"
kind: "vulnerability"
aliases: ["CVE-2026-61729"]
title: "SOCFortress CoPilot: hardcoded webhook secret lets anonymous callers bypass authentication"
severity: "critical"
cvss: 9.4
epss: null
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["graylog", "other", "self-hosted", "socfortress-copilot", "velociraptor", "wazuh"]
not_affected_if: ["changed-header-secrets", "no-wazuh-manager"]
published_at: "2026-10-30T15:16:53+00:00"
first_seen_at: "2026-10-30T15:31:11+00:00"
updated_at: "2026-10-30T15:33:11+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-61729", "first_seen_at": "2026-10-30T15:31:11+00:00"}]
---

# SOCFortress CoPilot: hardcoded webhook secret lets anonymous callers bypass authentication

SOCFortress CoPilot ships the same hardcoded fallback header value for its Graylog and Velociraptor webhooks, and the `.env.example` file contains it. An anonymous caller who sends that known value can skip the JWT login, forge alerts for any customer, and send attacker-chosen active-response commands to a configured Wazuh manager.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check whether `GRAYLOG_API_HEADER_VALUE` and `VELOCIRAPTOR_API_HEADER_VALUE` are unset or still equal the value in `.env.example`.
- Check the installed CoPilot version against `0.1.76`.
- Check whether a Wazuh manager is configured for active response.

## Fix

- Upgrade SOCFortress CoPilot to `0.1.76` or later.
- Set `GRAYLOG_API_HEADER_VALUE` and `VELOCIRAPTOR_API_HEADER_VALUE` to independent secrets that differ from the shipped default.

## Timeline

- 2026-10-30T15:31:11+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-61729

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_