github.com/ydb-platform/ydb-go-sdk/v3
Affected
- introduced
3.104.6, fixed3.134.2(semver)
Fixed versions
3.134.2
Fix
- Fixed version
3.134.2go get github.com/ydb-platform/ydb-go-sdk/[email protected]
Advisory
Also known as: GO-2026-4983
ydb-go-sdk's transactions are not committed using the options.WithCommit() option on last call table.Transaction.Execute in transaction
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.
Patchesydb-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
table.Transaction.CommitTx(ctx) instead use options.WithCommit().db.Table().DoTx(ctx, lambda) instead explicit start transaction on session.db.Query().Do(ctx, lambda) with the same logic in lambdaResources
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
Low Basis: The source's own band: LOW
3.104.6, fixed 3.134.2 (semver)3.134.2
3.134.2go get github.com/ydb-platform/ydb-go-sdk/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0