Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY2 SECURITY RECORDS

Temporal Technologies, Inc.

temporalio/sqlparser

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-65651 21 Sep 2026 temporalio/sqlparser: 0.0.0-20141206041240-1aae9baceee8 < 0.0.0-20260721183058-0466b6b405ac; Temporal Server: 0.0.0 < 0.10.0, 0.10.0 ≤ 1.29.7, 1.30.0 < 1.30.7, 1.31.0 < 1.31.3 Upgrade github.com/temporalio/sqlparser to v0.0.0-20260721183058-0466b6b405ac or later; v0.0.0-20260722001706-17d16cfe1da5 is the preferred upgrade. Temporal Server operators should upgrade to 1.30.7, 1.31.3, or 1.32.0, as appropriate for the deployed minor release line. The parser changes reject excessive nesting before recursive AST consumers receive an attacker-deep tree. Update reference ↗
CVE-2026-16651 21 Sep 2026 temporalio/sqlparser: 0.0.0-20180604150908-b055e9c9b4fa < 0.0.0-20260721183040-74181ffcbaaf; Temporal Server: 1.29.0 ≤ 1.29.7, 1.30.0 < 1.30.7, 1.31.0 < 1.31.3 Upgrade github.com/temporalio/sqlparser to v0.0.0-20260721183040-74181ffcbaaf or later. Temporal Server operators should upgrade to 1.30.7, 1.31.3, or 1.32.0, as appropriate for the deployed minor release line. The parser fix treats MySQL version comments as ordinary comments instead of interpreting their contents as SQL. Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.