CVE-2026-58490 · Other
NO FIX YET · SEE WHAT TO DO
Tracecat, a security automation platform, has a SAML setting that Docker Compose deployments can render empty, which turns off both signature checks on SAML logins. An unauthenticated attacker who can reach the SAML login endpoint can submit an unsigned forged response for an existing user's email and take over that session, including a superadmin account.
first public Jul 13, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running self-hosted Tracecat with Docker Compose and SAML enabled are exposed, if the SAML assertion endpoint is reachable. Default Fargate and Helm deployments are not affected, and exploitation does not create users when SAML user creation is disabled.
Not affected if fargate, helm, managed-hosting, saml-disabled, saml-user-creation-disabled
Who cares docker-compose, saml, self-hosted, tracecat
SAML_SIGNED_ASSERTIONS and SAML_SIGNED_RESPONSES in the rendered Compose configuration; empty values mean signatures are not required.1.0.0-beta.49.1.0.0-beta.49 removes the insecure deployment pass-through and requires signed assertions and responses.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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.