---
title: "CVE-2026-58490: Tracecat - Authentication Bypass"
description: "Tracecat 0.37.0 to 1.0.0-beta.49 contains an authentication bypass caused by empty SAML_SIGNED_ASSERTIONS and SAML_SIGNED_RESPONSES in Docker Compose deployments with SAML enabled, letting unauthenticated attackers forge unsigned responses to hijack user sessions, exploit requires access to SAML assertion consumer endpoint."
url: https://panop.io/threat-heartbeat/CVE-2026-58490/
---

# CVE-2026-58490 Tracecat - Authentication Bypass

Tracecat 0.37.0 to 1.0.0-beta.49 contains an authentication bypass caused by empty SAML\_SIGNED\_ASSERTIONS and SAML\_SIGNED\_RESPONSES in Docker Compose deployments with SAML enabled, letting unauthenticated attackers forge unsigned responses to hijack user sessions, exploit requires access to SAML assertion consumer endpoint.

CVSS base score 9.8 /10

Critical

CISA KEV

Not listed

Public exploit

None known

EPSS

0.34% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-58490)

## Details

Type

Authentication Bypass

Impact

Broken Authentication

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Published

6 November 2026

Updated

9 November 2026

Weakness

[CWE-347](https://cwe.mitre.org/data/definitions/347.html)

## Vendor fix

Upgrade to version 1.0.0-beta.49 or later.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-58490](https://nvd.nist.gov/vuln/detail/CVE-2026-58490)
- [https://github.com/TracecatHQ/tracecat/security/advisories/GHSA-6g53-h6fh-c3pj](https://github.com/TracecatHQ/tracecat/security/advisories/GHSA-6g53-h6fh-c3pj)
- [https://github.com/TracecatHQ/tracecat/commit/018258ba6a17c36cbfa7ca977526c34fb6afc35f](https://github.com/TracecatHQ/tracecat/commit/018258ba6a17c36cbfa7ca977526c34fb6afc35f)
- [https://github.com/TracecatHQ/tracecat/commit/a97aafbfd667a6b9a3b7b524e1c1bfa9d8c59779](https://github.com/TracecatHQ/tracecat/commit/a97aafbfd667a6b9a3b7b524e1c1bfa9d8c59779)
- [https://github.com/TracecatHQ/tracecat/commit/dab64eb7ac0eb2088783ca14f4cb2d058547bfff](https://github.com/TracecatHQ/tracecat/commit/dab64eb7ac0eb2088783ca14f4cb2d058547bfff)
- [https://github.com/TracecatHQ/tracecat/pull/2824](https://github.com/TracecatHQ/tracecat/pull/2824)
- [https://github.com/TracecatHQ/tracecat/pull/2825](https://github.com/TracecatHQ/tracecat/pull/2825)
- [https://github.com/TracecatHQ/tracecat/pull/2826](https://github.com/TracecatHQ/tracecat/pull/2826)
- [https://github.com/TracecatHQ/tracecat/releases/tag/1.0.0-beta.49](https://github.com/TracecatHQ/tracecat/releases/tag/1.0.0-beta.49)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)
