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
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
- Use explicit
table.Transaction.CommitTx(ctx)instead useoptions.WithCommit(). - Use transaction retrier
db.Table().DoTx(ctx, lambda)instead explicit start transaction on session. - Use query client
db.Query().Do(ctx, lambda)with the same logic inlambda
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
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
What each source reports
GitHub Advisories Score used
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.
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
- Use explicit
table.Transaction.CommitTx(ctx)instead useoptions.WithCommit(). - Use transaction retrier
db.Table().DoTx(ctx, lambda)instead explicit start transaction on session. - Use query client
db.Query().Do(ctx, lambda)with the same logic inlambda
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
- Record
GHSA-28xx-pppm-vqff- CVSS 4.0
- 2.7 Low
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 - Weakness
- CWE-670
- Updated
- 2026-11-02
OSV
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.
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
- Use explicit
table.Transaction.CommitTx(ctx)instead useoptions.WithCommit(). - Use transaction retrier
db.Table().DoTx(ctx, lambda)instead explicit start transaction on session. - Use query client
db.Query().Do(ctx, lambda)with the same logic inlambda
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
- Record
GHSA-28xx-pppm-vqff- CVSS 4.0
- 2.7 Low
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 - Weakness
- CWE-670
- Updated
- 2026-11-02
OSVGO-2026-4983No score
ydb-go-sdk's transactions are not committed using the `options.WithCommit()` option on last call `table.Transaction.Execute` in transaction in github.com/ydb-platform/ydb-go-sdk
ydb-go-sdk's transactions are not committed using the options.WithCommit() option on last call table.Transaction.Execute in transaction in github.com/ydb-platform/ydb-go-sdk
- Record
GO-2026-4983- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
github.com/ydb-platform/ydb-go-sdk/v3Go | 3.104.6 to 3.134.1 | 3.134.2 |
github.com/ydb-platform/ydb-go-sdk/v3Go | 3.104.6 up to 3.134.2 | 3.134.2 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-28xx-pppm-vqff is a low vulnerability (CVSS 2.7) in github.com/ydb-platform/ydb-go-sdk/v3, published April 30, 2026. No source lists public exploit code. Fixed in github.com/ydb-platform/ydb-go-sdk/v3 3.134.2.
References
github.com/ydb-platform/ydb-go-sdk/security/advisories/GHSA-28xx-pppm-vqff