Unsigned SAML response accepted in Tracecat Docker Compose deployments
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-347.
Summary
Tracecat, an open-source security automation platform, from 0.37.0 before 1.0.0-beta.49 renders SAML_SIGNED_ASSERTIONS and SAML_SIGNED_RESPONSES as empty values in Docker Compose deployments with SAML enabled, disabling both signature requirements. This is an improper verification of cryptographic signature (CWE-347) that lets an unauthenticated remote attacker who can reach the SAML assertion consumer endpoint submit a forged unsigned response for an existing user email address and obtain that user's session. Targeting an existing superadmin can lead to superadmin account takeover, but exploitation does not create users when SAML user creation is disabled.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
Description from the CNA
Tracecat is an open-source security automation platform for teams and AI agents. From version 0.37.0 until 1.0.0-beta.49, Docker Compose deployments with SAML enabled can render SAML_SIGNED_ASSERTIONS and SAML_SIGNED_RESPONSES as empty values, overriding secure application defaults and disabling both signature requirements. An unauthenticated attacker who can reach the SAML assertion consumer endpoint can submit a forged unsigned response for an existing Tracecat user email address and obtain that user’s session. Targeting an existing superadmin can result in superadmin account takeover. Exploitation does not create users when SAML user creation is disabled and does not affect default Fargate or Helm deployments. Version 1.0.0-beta.49 removes the insecure deployment pass-through and requires signed assertions and responses.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| TracecatHQ | tracecat | 0.37.0 to before 1.0.0-beta.49 | 1.0.0-beta.49 | Patch available | CNA |
- tracecat VendorTracecatHQ Affected 0.37.0 to before 1.0.0-beta.49 Fixed in 1.0.0-beta.49 Patch available CNA
Remediation
Upgrade Tracecat to version 1.0.0-beta.49, which removes the insecure deployment pass-through and requires signed assertions and responses.
Written with Claude Haiku 5.5 from the sources below · 2026-11-06
- Fix · CNA tracecat (TracecatHQ) Fixed in 1.0.0-beta.49
Timeline
- 2026-11-06 Threatist record created from CVE-2026-58490
References
Other 8
- https://github.com/TracecatHQ/tracecat/security/advisories/GHSA-6g53-h6fh-c3pj
- https://github.com/TracecatHQ/tracecat/pull/2824
- https://github.com/TracecatHQ/tracecat/pull/2825
- https://github.com/TracecatHQ/tracecat/pull/2826
- https://github.com/TracecatHQ/tracecat/commit/018258ba6a17c36cbfa7ca977526c34fb6afc35f
- https://github.com/TracecatHQ/tracecat/commit/a97aafbfd667a6b9a3b7b524e1c1bfa9d8c59779
- https://github.com/TracecatHQ/tracecat/commit/dab64eb7ac0eb2088783ca14f4cb2d058547bfff
- https://github.com/TracecatHQ/tracecat/releases/tag/1.0.0-beta.49
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences