Summary
ydb-go-sdk's transactions are not committed using the options.WithCommit() option on last call table.Transaction.Execute in transaction
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
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
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).
Frequently Asked Questions
- What is GHSA-28XX-PPPM-VQFF? GHSA-28XX-PPPM-VQFF is a low-severity security vulnerability in github.com/ydb-platform/ydb-go-sdk/v3 (go), affecting versions >= 3.104.6, <= 3.134.1. It is fixed in 3.134.2.
- Which versions of github.com/ydb-platform/ydb-go-sdk/v3 are affected by GHSA-28XX-PPPM-VQFF? github.com/ydb-platform/ydb-go-sdk/v3 (go) versions >= 3.104.6, <= 3.134.1 is affected.
- Is there a fix for GHSA-28XX-PPPM-VQFF? Yes. GHSA-28XX-PPPM-VQFF is fixed in 3.134.2. Upgrade to this version or later.
- Is GHSA-28XX-PPPM-VQFF exploitable, and should I be worried? Whether GHSA-28XX-PPPM-VQFF is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-28XX-PPPM-VQFF is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-28XX-PPPM-VQFF? Upgrade
github.com/ydb-platform/ydb-go-sdk/v3to 3.134.2 or later.