TracecatHQ Tracecat up to 1.0.0-beta.48 SAML Authentication improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.42+ |
Summary
A vulnerability classified as critical has been found in TracecatHQ Tracecat up to 1.0.0-beta.48. Affected is an unknown function of the component SAML Authentication. Performing a manipulation results in improper authentication. This vulnerability was named CVE-2026-58490. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability was found in TracecatHQ Tracecat up to 1.0.0-beta.48. It has been classified as critical. This affects some unknown processing of the component SAML Authentication. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-58490 since 06/30/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 1.0.0-beta.49 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
- 1.0.0-beta.0
- 1.0.0-beta.1
- 1.0.0-beta.2
- 1.0.0-beta.3
- 1.0.0-beta.4
- 1.0.0-beta.5
- 1.0.0-beta.6
- 1.0.0-beta.7
- 1.0.0-beta.8
- 1.0.0-beta.9
- 1.0.0-beta.10
- 1.0.0-beta.11
- 1.0.0-beta.12
- 1.0.0-beta.13
- 1.0.0-beta.14
- 1.0.0-beta.15
- 1.0.0-beta.16
- 1.0.0-beta.17
- 1.0.0-beta.18
- 1.0.0-beta.19
- 1.0.0-beta.20
- 1.0.0-beta.21
- 1.0.0-beta.22
- 1.0.0-beta.23
- 1.0.0-beta.24
- 1.0.0-beta.25
- 1.0.0-beta.26
- 1.0.0-beta.27
- 1.0.0-beta.28
- 1.0.0-beta.29
- 1.0.0-beta.30
- 1.0.0-beta.31
- 1.0.0-beta.32
- 1.0.0-beta.33
- 1.0.0-beta.34
- 1.0.0-beta.35
- 1.0.0-beta.36
- 1.0.0-beta.37
- 1.0.0-beta.38
- 1.0.0-beta.39
- 1.0.0-beta.40
- 1.0.0-beta.41
- 1.0.0-beta.42
- 1.0.0-beta.43
- 1.0.0-beta.44
- 1.0.0-beta.45
- 1.0.0-beta.46
- 1.0.0-beta.47
- 1.0.0-beta.48
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 9.8
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Tracecat 1.0.0-beta.49
Timeline
06/30/2026 CVE reserved11/06/2026 Advisory disclosed
11/06/2026 VulDB entry created
11/06/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CNA: GitHub_M
CVE: CVE-2026-58490 (🔒)
GCVE (CVE): GCVE-0-2026-58490
GCVE (VulDB): GCVE-100-432123
Entry
Created: 11/06/2026 21:26Changes: 11/06/2026 21:26 (64)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.