PT-2026-39553 · Go · Github.Com/Ydb-Platform/Ydb-Go-Sdk/V3

Published

2026-04-30

·

Updated

2026-04-30

CVSS v4.0

2.7

Low

VectorAV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U

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

Fix

Found an issue in the description? Have something to add? Feel free to write us 👾
dbugs@ptsecurity.com

Weakness Enumeration

CWE-670

Related Identifiers

GHSA-28XX-PPPM-VQFF

Affected Products

Github.Com/Ydb-Platform/Ydb-Go-Sdk/V3