External risk intelligence

Tracecat SAML Signature Bypass Allows Session Takeover

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-58490

Tracecat is a security automation platform often deployed as a web application. The vulnerability affects the SAML assertion consumer endpoint. Because identity providers and automation platforms are commonly exposed to the internet to facilitate remote user access and external integrations, the vulnerable endpoint is likely to be reachable from the public internet in many standard deployments.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory details a critical vulnerability in Tracecat, an open-source security automation platform, affecting specific Docker Compose deployments with SAML enabled. The issue allows an unauthenticated attacker to potentially hijack user sessions, including superadmin accounts, by submitting forged, unsigned SAML responses. The primary concern is confirming if your Tracecat deployment uses SAML and is exposed in a way that could be targeted.

Unsigned responses can take over user accounts.
Affects security platforms, critical for your defenses.
Confirm SAML usage and exposure to confirm relevance.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker could reach the SAML assertion consumer endpoint of a vulnerable Tracecat deployment. By submitting a forged, unsigned SAML response for an existing user, an attacker can obtain that user's session, potentially leading to superadmin account takeover. This is applicable to Docker Compose deployments with SAML enabled.

Attacker can reach the SAML endpoint.
Forged unsigned SAML response is submitted.
Risk of superadmin account takeover.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, Docker Compose deployments of Tracecat with SAML enabled could allow an unauthenticated attacker to bypass signature verification for SAML responses, potentially leading to session hijacking. This could affect user sessions and sensitive information when targeting existing user accounts.

User sessions and sensitive information.
Forged SAML responses can hijack sessions.
Account takeover, especially for superadmins.

Operational Fix

Recommended remediation, mitigation, and detection steps

Tracecat's Docker Compose deployments with SAML enabled are at risk. The platform team responsible for Tracecat, in coordination with security operations, should identify all such deployments, confirm reachability and business criticality, and prioritize remediation. The first practical move is to locate Tracecat instances using SAML in Docker Compose, ascertain their exposure, and then plan updates or alternative controls.

Platform team owns remediation.
Verify SAML reachability and criticality.
Plan Docker Compose updates and audits.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is Tracecat?

Tracecat is an open-source platform designed for security teams to automate workflows and manage AI agents. It acts as a centralized engine for security operations, often handling sensitive integration data and authentication processes. Because it manages automated tasks, it frequently requires robust identity verification to ensure only authorized users control its internal workflows and administrative functions.

What is the vulnerability in CVE-2026-58490?

This CVE involves a weakness classified as CWE-347: Improper Verification of Cryptographic Signature. In affected Tracecat versions, the system can incorrectly process SAML authentication data by treating signed assertions or responses as empty. This logic error effectively disables the required security checks, allowing the system to accept forged, unsigned identity responses as valid, which leads to unauthorized session hijacking.

How does an attacker trigger this SAML flaw?

An attacker triggers this by sending a forged, unsigned SAML response directly to the platform's assertion consumer endpoint. This attack requires the deployment to have SAML enabled via Docker Compose. Importantly, this does not affect default Fargate or Helm deployments. Furthermore, if SAML user creation is disabled, the attack cannot be used to create new unauthorized accounts; it only targets existing users.

Is my Tracecat instance at risk?

According to Halo Surface Signal, this vulnerability is critical for instances reachable from the public internet. Because Tracecat is often deployed as a web application to support remote access and external integrations, its SAML endpoint is frequently exposed. If your instance is internet-facing and uses the vulnerable Docker Compose configuration, it is likely reachable and at higher risk.

How do I secure my Tracecat deployment?

First, identify if you are running Tracecat using Docker Compose with SAML enabled. If so, plan to update to version 1.0.0-beta.49 or later, which removes the insecure deployment pass-through and enforces strict signature requirements for all SAML assertions and responses. Prioritize this update for any instances that are accessible over the network.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.