Skip to main content
veriom
Menu

Explore Veriom products, resources, and account pages.

CVE-2026-58490TracecatHQ tracecat improper signature verification

High priorityCritical9.8EPSS not scored yet

CVE-2026-58490 is a improper signature verification in TracecatHQ tracecat, rated critical (9.8 on CVSS 3.1).

Why this priority: Critical, and reachable over the network without an account.

Published · Updated · NVD status: Received

What it is

A cryptographic signature is not checked properly, so forged data is accepted.

How it is reached

An attacker can exploit it over the network, without an account, and nobody has to click anything.

What an attacker gains

A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker read or tamper with traffic, or pass a forged message as genuine.

Is it being exploited?

There is no public report of exploitation yet. It can be exploited automatically, at scale.

What to do

  1. Upgrade TracecatHQ tracecat to 1.0.0-beta.49 or later.
  2. Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.

Description from NVD

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.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • TLS termination and service-to-service channels. The flaw sits on the network path between clients and services.
  • Signature checks. The flaw sits on the network path between clients and services.

Trust boundaries in play

  • Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
  • On the network path between clients and services. An attacker who crosses it can read or tamper with traffic, or pass a forged message as genuine.

Questions to answer about your own systems

  • Where does TracecatHQ tracecat run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?
See how Veriom maps an architectureTake the interactive tour

Read more

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.