How severe is GHSA-qr2g-p6q7-w82m?

No CVSS score has been assigned to GHSA-qr2g-p6q7-w82m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qr2g-p6q7-w82m?

GHSA-qr2g-p6q7-w82m affects the following packages: github.com/coinbase/x402/go (Go), @x402/svm (npm), x402 (PyPI). Ecosystems affected: Go, npm, PyPI.

How do I fix GHSA-qr2g-p6q7-w82m?

Update github.com/coinbase/x402/go to 2.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qr2g-p6q7-w82m is resolved across your whole dependency graph.

How do I detect GHSA-qr2g-p6q7-w82m in my Go, npm, PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/coinbase/x402/go, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-qr2g-p6q7-w82m 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.

How does O3 Security protect against GHSA-qr2g-p6q7-w82m?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qr2g-p6q7-w82m can be triaged on real exposure rather than presence alone.

Is GHSA-qr2g-p6q7-w82m actively exploited in the wild?

No public exploit code has been indexed for GHSA-qr2g-p6q7-w82m 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-qr2g-p6q7-w82m published, and has it been updated?

GHSA-qr2g-p6q7-w82m was published on March 7, 2026 and was last updated on April 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📦 npm🐍 PyPI

Not in CISA KEV

GHSA-qr2g-p6q7-w82m — go

GHSA-qr2g-p6q7-w82m is a security vulnerability in github.com/coinbase/x402/go. A fix is available for github.com/coinbase/x402/go — see the affected versions and patch details below.

x402 SDK Security Advisory

Also known asGO-2026-4647

Published

Mar 7, 2026

Updated

Apr 8, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

161other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@x402/svmnpm

60Kdownloads / week

Description

Impact

A security vulnerability exists in outdated versions of the x402 SDK.

This vulnerability does not affect users' private keys, smart contracts, or funds.

The issue impacts resource servers accepting payments on Solana when the facilitator is running a vulnerable version of the x402 SDK.

Who Should Take Action

Facilitators that process payments on Solana must upgrade the x402 SDK to the patched versions listed below.

Clients are not required to upgrade.

Resource servers are not required to upgrade unless they operate their own facilitator (self-facilitate).

Patches

Please update to the following package versions:

Npm: @x402/svm >= 2.6.0
Pypi: x402 >= 2.3.0
Go: x402 >= 2.5.0

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/coinbase/x402/go`	all versions	2.5.0`go get github.com/coinbase/x402/go@v2.5.0`
📦npm	`@x402/svm`	all versions	2.6.0`npm install @x402/svm@2.6.0`
🐍PyPI	`x402`	all versions	2.3.0`pip install --upgrade 'x402==2.3.0'`

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/coinbase/x402/go, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/coinbase/x402/go to 2.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qr2g-p6q7-w82m 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-qr2g-p6q7-w82m can be triaged on real exposure rather than presence alone.

Tailored to GHSA-qr2g-p6q7-w82m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A security vulnerability exists in outdated versions of the x402 SDK. This vulnerability does not affect users' private keys, smart contracts, or funds. The issue impacts resource servers accepting payments on Solana when the facilitator is running a vulnerable version of the x402 SDK. ### Who Should Take Action Facilitators that process payments on Solana must upgrade the x402 SDK to the patched versions listed below. Clients are not required to upgrade. Resource servers are not required to upgrade unless they operate their own facilitator (self-facilitate). ### Patches Pl

O3 Security · Impact-Aware SCA

Is GHSA-qr2g-p6q7-w82m in your dependencies?

O3 Security finds GHSA-qr2g-p6q7-w82m across Go, npm, PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works