GitHub Advisoryadvisory · Go

GHSA-28xx-pppm-vqff ydb-go-sdk's transactions are not committed using the `options.WithCommit()` option on last call `table.Transaction.Execute` in transaction

LOW Published 2026-04-30 Modified 2026-06-08 Official page ↗
Ecosystem
Go
Packages
github.com/ydb-platform/ydb-go-sdk/v3
Severity
Low
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
Weaknesses
CWE-670
Reviewed
2026-04-30

Affected packages

• Go github.com/ydb-platform/ydb-go-sdk/v3: >= 3.104.6, < 3.134.2 → fixed in 3.134.2

Description

Impact Transactions were NOT committed despite the explicit `options.WithCommit` flag using table service client. Because of this, clients did not commit changes to the transaction, relying on the fact that the transaction commit was successful. This led (in rare cases) to a loss of data consistency. Patches `ydb-go-sdk` contains this problem in versions from v3.104.6 to v3.134.1. The fix for this problem has been released in version v3.134.2 (https://github.com/ydb-platform/ydb-go-sdk/pull/2091). Workarounds 1) Use explicit `table.Transaction.CommitTx(ctx)` instead use `options.WithCommit()`. 2) Use transaction retrier `db.Table().DoTx(ctx, lambda)` instead explicit start transaction on session. 3) Use query client `db.Query().Do(ctx, lambda)` with the same logic in `lambda` Resources Commit with bug https://github.com/ydb-platform/ydb-go-sdk/commit/251128a64763555d9a79ee7a131dd154c9000eb9 Commit with fix https://github.com/ydb-platform/ydb-go-sdk/commit/25dcff4c41153f1f9413512ba12999b40bf7154d

Related

Weakness · CWE (1)

  • CWE-670 Always-Incorrect Control Flow Implementation weakness

References