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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.7 · 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 · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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

Published by the source

30 Apr 2026, 18:21 UTC

Last modified by the source

30 Apr 2026, 18:21 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-28xx-pppm-vqff

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-28xx-pppm-vqff

Advisory: ydb-go-sdk's transactions are not committed using the `options.WithCommit()` option on last call `table.Transaction.Execute` in transaction
IDs: GHSA-28xx-pppm-vqff
Record: https://patchnext.com/advisories/ghsa-28xx-pppm-vqff (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/ydb-platform/ydb-go-sdk/v3 3.134.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/ydb-platform/ydb-go-sdk/v3: affected >= 3.104.6, <= 3.134.1; fixed in 3.134.2

## Suggested inspection (read-only)
- Go github.com/ydb-platform/ydb-go-sdk/v3: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/ydb-platform/ydb-go-sdk/v3.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-28xx-pppm-vqff (GitHub-reviewed advisory GHSA-28xx-pppm-vqff lists affected ranges: Go github.com/ydb-platform/ydb-go-sdk/v3 >=3.104.6 <=3.134.1)

Commands are suggestions: review each one before running it.