GHSA-28xx-pppm-vqff — v3
Fix: ydb-platform/ydb-go-sdk#2091GHSA-28xx-pppm-vqff is a security vulnerability in github.com/ydb-platform/ydb-go-sdk/v3. A fix is available for github.com/ydb-platform/ydb-go-sdk/v3 — see the affected versions and patch details below.
ydb-go-sdk's transactions are not committed using the `options.WithCommit()` option on last call `table.Transaction.Execute` in transaction
Real-World Exposure
github.com/ydb-platform/ydb-go-sdk/v3Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/ydb-platform/ydb-go-sdk/v3 | ≥ 3.104.6&&< 3.134.2 | 3.134.2go get github.com/ydb-platform/ydb-go-sdk/v3@v3.134.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ydb-platform/ydb-go-sdk/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/ydb-platform/ydb-go-sdk/v3 to 3.134.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-28xx-pppm-vqff is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-28xx-pppm-vqff can be triaged on real exposure rather than presence alone.
Tailored to GHSA-28xx-pppm-vqff. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-28xx-pppm-vqff in your dependencies?
O3 Security finds GHSA-28xx-pppm-vqff across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.