How severe is GHSA-28xx-pppm-vqff?

No CVSS score has been assigned to GHSA-28xx-pppm-vqff yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-28xx-pppm-vqff?

GHSA-28xx-pppm-vqff affects the following packages: github.com/ydb-platform/ydb-go-sdk/v3 (Go). Ecosystems affected: Go.

How do I fix GHSA-28xx-pppm-vqff?

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.

How do I detect GHSA-28xx-pppm-vqff in my Go dependencies?

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.

How do I mitigate GHSA-28xx-pppm-vqff if there is no patch (or I can't update yet)?

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.

Is GHSA-28xx-pppm-vqff actively exploited in the wild?

No public exploit code has been indexed for GHSA-28xx-pppm-vqff yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-28xx-pppm-vqff published, and has it been updated?

GHSA-28xx-pppm-vqff was published on April 30, 2026 and was last updated on June 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

ydb-go-sdk's transactions are not committed using the `options.WithCommit()` option on last call `table.Transaction.Execute` in transactionGHSA-28xx-pppm-vqff

Fix: ydb-platform/ydb-go-sdk#2091

GHSA-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.

Also known asGO-2026-4983

Published

Apr 30, 2026

Updated

Jun 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 8, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/ydb-platform/ydb-go-sdk/v3

Real-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 use options.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 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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/ydb-platform/ydb-go-sdk/v3`	≥ 3.104.6&&< 3.134.2	3.134.2`go get github.com/ydb-platform/ydb-go-sdk/v3@v3.134.2`

Detection & mitigation playbook

Open-source dependency

Detect
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.

Frequently Asked Questions

### 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](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:

O3 Security · Impact-Aware SCA

Is GHSA-28xx-pppm-vqff in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works