Skip to content

Vendor

Temporal Technologies, Inc. vulnerabilities

5 published CVES affecting Temporal Technologies, Inc., from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
5
Critical
0
High
0
Medium
2
Low
3
Unscored
0
CISA KEV
0
Atom feed of Temporal Technologies, Inc. alerts

Products

Latest Temporal Technologies, Inc. CVEs

Newest publication first

  1. MediumCVSS 6.3 EPSS 0.61%

    The frontend gRPC server's streaming interceptor chain did not include the authorization interceptor. When a ClaimMapper and Authorizer are configured, unary RPCs enforce authentication and authorization, but the streaming AdminService/StreamWorkflowReplicationMessages endpoint a...

  2. LowCVSS 2.3 EPSS 0.34%

    A writer role user in an attacker-controlled namespace could signal, delete, and reset workflows or activities in a victim namespace on the same cluster. Exploitation requires the attacker to know or guess specific victim workflow ID(s) and, for signal operations, signal names. T...

  3. LowCVSS 2.0 EPSS 0.09%

    The Temporal api-go library prior to version 1.44.1 did not send update response information to Data Converter when the proxy package within the api-go module was used in a gRPC proxy prior to transmission. This resulted in information contained within the update response field n...

  4. MediumCVSS 4.4 EPSS 0.49%

    Denial of Service in Temporal Server prior to version 1.20.5, 1.21.6, and 1.22.7 allows an authenticated user who has permissions to interact with workflows and has crafted an invalid UTF-8 string for submission to potentially cause a crashloop. If left unchecked, the task contai...

  5. LowCVSS 3.6 EPSS 0.17%

    Insecure defaults in open-source Temporal Server before version 1.20 on all platforms allows an attacker to craft a task token with access to a namespace other than the one specified in the request. Creation of this task token must be done outside of the normal Temporal server fl...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.