{"answers":{"affected":"3 open source packages ship an affected version, including github.com/ydb-platform/ydb-go-sdk/v3.","exploited":"There is no known exploitation of GHSA-28xx-pppm-vqff in the wild and no public exploit code.","fix":"Upgrade github.com/ydb-platform/ydb-go-sdk/v3 to 3.134.2 or later.","what":"GHSA-28xx-pppm-vqff is a vulnerability in github.com/ydb-platform/ydb-go-sdk/v3, published on 30 Apr 2026."},"fix_prompt":"Check this codebase for GHSA-28xx-pppm-vqff and fix it if it is affected.\n\nWhat it is: GHSA-28xx-pppm-vqff is a vulnerability in github.com/ydb-platform/ydb-go-sdk/v3, published on 30 Apr 2026. \nExploitation: There is no known exploitation of GHSA-28xx-pppm-vqff in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/ydb-platform/ydb-go-sdk/v3 (Go): affected from 3.104.6; fixed in 3.134.2\n- github.com/ydb-platform/ydb-go-sdk/v3 (Go): affected from 3.104.6; fixed in 3.134.2\n- github.com/ydb-platform/ydb-go-sdk/v3 (Go): affected from 3.104.6; fixed in 3.134.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-28xx-pppm-vqff/ (Markdown: https://insights.sbomify.com/GHSA-28xx-pppm-vqff/index.md)","id":"GHSA-28xx-pppm-vqff","markdown":"https://insights.sbomify.com/GHSA-28xx-pppm-vqff/index.md","name":"GHSA-28xx-pppm-vqff","record":{"aliases":["GO-2026-4983"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"unknown","non_default_config":false,"product_category":"Go database SDK","requires_auth":"none","summary":"A bug in the ydb-go-sdk library causes transactions to silently fail to commit, leading to potential data inconsistency for applications relying on the WithCommit option.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\nTransactions 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.\n\n### Patches\n`ydb-go-sdk` contains this problem in versions from [v3.104.6](https://github.com/ydb-platform/ydb-go-sdk/releases/tag/v3.104.6) to [v3.134.1](https://github.com/ydb-platform/ydb-go-sdk/releases/tag/v3.134.1). The fix for this problem has been released in version [v3.134.2](https://github.com/ydb-platform/ydb-go-sdk/releases/tag/v3.134.2) (https://github.com/ydb-platform/ydb-go-sdk/pull/2091).\n\n### Workarounds\n1) Use explicit `table.Transaction.CommitTx(ctx)` instead use `options.WithCommit()`.\n2) Use transaction retrier `db.Table().DoTx(ctx, lambda)` instead explicit start transaction on session.\n3) Use query client `db.Query().Do(ctx, lambda)` with the same logic in `lambda`\n\n### Resources\nCommit with bug https://github.com/ydb-platform/ydb-go-sdk/commit/251128a64763555d9a79ee7a131dd154c9000eb9\nCommit with fix https://github.com/ydb-platform/ydb-go-sdk/commit/25dcff4c41153f1f9413512ba12999b40bf7154d","ecosystems":["Go"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Impact Transactions were NOT committed despite the explicit `options.WithCommit` flag using table service client.","id":"GHSA-28xx-pppm-vqff","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Go","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"Go","fixed":["3.134.2"],"introduced":["3.104.6"],"last_affected":[],"package":"github.com/ydb-platform/ydb-go-sdk/v3","purl":null,"source":"GHSA-28xx-pppm-vqff"},{"ecosystem":"Go","fixed":["3.134.2"],"introduced":["3.104.6"],"last_affected":[],"package":"github.com/ydb-platform/ydb-go-sdk/v3","purl":"pkg:golang/github.com/ydb-platform/ydb-go-sdk/v3","source":"GHSA-28xx-pppm-vqff"},{"ecosystem":"Go","fixed":["3.134.2"],"introduced":["3.104.6"],"last_affected":[],"package":"github.com/ydb-platform/ydb-go-sdk/v3","purl":"pkg:golang/github.com/ydb-platform/ydb-go-sdk/v3","source":"GO-2026-4983"}],"products":null,"published":"2026-04-30","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A bug in the ydb-go-sdk library causes transactions to silently fail to commit, leading to potential data inconsistency for applications relying on the WithCommit option.","url":"https://insights.sbomify.com/GHSA-28xx-pppm-vqff/"}