CVE-2026-61729

SOCFortress CoPilot: Hardcoded Default Header Secret - Unauthenticated Active-Response Invocation and Alert Injection

Published Oct 30, 2026 CVSS 3.1 · 9.4 Critical EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Prior to version 0.1.76, SOCFortress CoPilot’s webhook handlers for Graylog and Velociraptor used a hard‑coded header value as a fallback when the configuration values were unset. An attacker who supplies this known header can bypass the JWT authentication required by normal API calls. Once authenticated, the /api/graylog/invoke endpoint accepts arbitrary COMMAND, ACTION, VALUE, and AGENT_ID values and forwards them to the configured Wazuh manager without performing the command‑enum validation that the authenticated route performs, allowing disruptive or malicious scripts to run on endpoints. Additionally, the /api/incidents/alerts/create/threshold and /api/incidents/alerts/create/velo-sigma endpoints accept forged alerts with arbitrary customer_code values and forward attacker‑controlled OpenSearch queries, permitting information disclosure or injection attacks.

Affected Systems

SocFortress CoPilot releases earlier than 0.1.76 are affected. Any deployment that has not overridden the GRAYLOG_API_HEADER_VALUE or VELOCIRAPTOR_API_HEADER_VALUE in its environment configuration remains vulnerable. Deployments that have deliberately changed these header secrets are not exposed to the default‑secret bypass.

Risk and Exploitability

The CVSS score of 9.4 marks this flaw as critical. Although EPSS data is unavailable, the publicly known default secret reduces the effort and skill needed for exploitation, implying a high likelihood of attack. The issue is not listed in the CISA KEV catalog. An attacker can trigger the vulnerability by sending HTTP POST requests to the affected endpoints, supplying the known header value, and tailoring the payloads to exploit the lack of input validation. Successful exploitation allows remote execution of arbitrary commands on the Wazuh manager and manipulation of OpenSearch queries against the target environment.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to version 0.1.76 or later, where the hardcoded default header has been removed.
  • Replace the GRAYLOG_API_HEADER_VALUE and VELOCIRAPTOR_API_HEADER_VALUE in the runtime configuration with unique, strong secrets and ensure they are not left at the shipped example values.
  • Verify that JWT authentication is enforced on all publicly exposed API endpoints to prevent anonymous access.
  • Optionally, disable or restrict the active‑response and incident‑alert webhook endpoints if they are not required in your environment.

Generated by OpenCVE AI on October 30, 2026 at 16:15 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Socfortress
Socfortress copilot
Vendors & Products Socfortress
Socfortress copilot
Type Values Removed Values Added
Description 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.
Title SOCFortress CoPilot: Hardcoded Default Header Secret - Unauthenticated Active-Response Invocation and Alert Injection
Weaknesses CWE-306
CWE-798
References
Metrics cvssV3_1

{'score': 9.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H'}

Weaknesses
  • CWE-306

    Missing Authentication for Critical Function

  • CWE-798

    Use of Hard-coded Credentials

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 5, 2026, 9:36 PM
Reserved
Jul 10, 2026, 6:59 PM
Status
Deferred
Published
Oct 30, 2026, 3:16 PM
Modified
Nov 5, 2026, 10:18 PM