Advisory

GHSA-28xx-pppm-vqff

Also known as: GO-2026-4983

Summary

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

Details

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

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-04-30 18:21 UTC
Modified
2026-06-08 20:10 UTC

Affected packages and fixes

github.com/ydb-platform/ydb-go-sdk/v3

Go · All systems

Affected

  • introduced 3.104.6, fixed 3.134.2 (semver)

Fixed versions

3.134.2

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences