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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.0.0-beta.49
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Tracecat Docker Compose deployment is affected (version 0.37.0 up to 1.0.0-beta.48) SAML SSO is enabled, for example by including saml in TRACECAT__AUTH_TYPES SAML_SIGNED_ASSERTIONS is unset, empty, or resolves to false SAML_SIGNED_RESPONSES is unset, empty, or resolves to false The deployment uses the affected Docker Compose environment defaults
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 22/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 9.8
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Tracecat Docker Compose deployment is affected (version 0.37.0 up to 1.0.0-beta.48) SAML SSO is enabled, for example by including saml in TRACECAT__AUTH_TYPES SAML_SIGNED_ASSERTIONS is unset, empty, or resolves to false SAML_SIGNED_RESPONSES is unset, empty, or resolves to false The deployment uses the affected Docker Compose environment defaultsUpgrade to a fixed version: 1.0.0-beta.49.
Workaround: Explicitly set SAML_SIGNED_ASSERTIONS = true and SAML_SIGNED_RESPONSES = true
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- TracecatHQ tracecat
From 0.37.0 · fixed in 1.0.0-beta.49
Evidence 8
- Advisory
- Repository
- Repository
- Repository
- Repository
Show all 8 sourcesShow fewer sources
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-58490
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: cve.now feed data
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: github.com
Which versions are affected by CVE-2026-58490?
tracecat: from 0.37.0 before 1.0.0-beta.49.Source: cve.now feed data
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: github.com
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: github.com