---
id: "CVE-2026-58490"
page: "https://infrastack.ai/live/CVE-2026-58490"
kind: "vulnerability"
aliases: ["CVE-2026-58490"]
title: "Tracecat: forged SAML login grants session as any existing user"
severity: "critical"
cvss: 9.8
epss: null
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["docker-compose", "other", "saml", "self-hosted", "tracecat"]
not_affected_if: ["fargate", "helm", "managed-hosting", "saml-disabled", "saml-user-creation-disabled"]
published_at: "2026-11-06T20:17:23+00:00"
first_seen_at: "2026-11-06T20:44:00+00:00"
updated_at: "2026-11-06T20:44:10+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-58490", "first_seen_at": "2026-11-06T20:44:00+00:00"}]
exploit_sources: []
---

# Tracecat: forged SAML login grants session as any existing user

Link for people: https://infrastack.ai/live/CVE-2026-58490 (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check whether the deployment uses Docker Compose with SAML enabled, for example by looking for SAML settings in the Compose environment.
- Check the values of `SAML_SIGNED_ASSERTIONS` and `SAML_SIGNED_RESPONSES` in the rendered Compose configuration; empty values mean signatures are not required.
- Check the installed Tracecat version against the affected range from 0.37.0 up to but not including `1.0.0-beta.49`.

## Fix

- Tracecat `1.0.0-beta.49` removes the insecure deployment pass-through and requires signed assertions and responses.

## Timeline

- 2026-11-06T20:44:00+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-58490

## Documents

- [advisory] Vendor advisory: github.com https://github.com/TracecatHQ/tracecat/security/advisories/GHSA-6g53-h6fh-c3pj
- [fix] Patch: github.com https://github.com/TracecatHQ/tracecat/commit/018258ba6a17c36cbfa7ca977526c34fb6afc35f
- [fix] Patch: github.com https://github.com/TracecatHQ/tracecat/commit/a97aafbfd667a6b9a3b7b524e1c1bfa9d8c59779
- [fix] Patch: github.com https://github.com/TracecatHQ/tracecat/commit/dab64eb7ac0eb2088783ca14f4cb2d058547bfff
- [fix] Release notes: github.com https://github.com/TracecatHQ/tracecat/releases/tag/1.0.0-beta.49

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_