# GHSA-3j63-5h8p-gf7c: x402 SDK vulnerable in outdated versions in resource servers for builders

> Outdated x402 SDK versions pose a security risk to builders operating resource servers, requiring an upgrade to patched versions.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 20 Aug 2025

## What is GHSA-3j63-5h8p-gf7c?

GHSA-3j63-5h8p-gf7c is a vulnerability in x402, published on 20 Aug 2025. It can be exploited over the network.

### Official description

### Impact
There is a security vulnerability in outdated versions of the x402 SDK. This does not directly affect users' keys, smart contracts, or funds.

This primarily impacts builders working on resource servers.

### Patches
Please update to the following package versions:
* x402 >= 0.5.2
* x402-next >= 0.5.2
* x402-express >= 0.5.2
* x402-hono >= 0.5.2

## Which versions are affected by GHSA-3j63-5h8p-gf7c?

8 open source packages ship an affected version, including x402, x402-express and x402-hono.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `x402` | npm | All versions | 0.5.2 |
| `x402` | npm | All versions | 0.5.2 |
| `x402-express` | npm | All versions | 0.5.2 |
| `x402-express` | npm | All versions | 0.5.2 |
| `x402-hono` | npm | All versions | 0.5.2 |
| `x402-hono` | npm | All versions | 0.5.2 |
| `x402-next` | npm | All versions | 0.5.2 |
| `x402-next` | npm | All versions | 0.5.2 |

## How do I fix GHSA-3j63-5h8p-gf7c?

Upgrade x402 to 0.5.2 or later.

## Is GHSA-3j63-5h8p-gf7c being exploited?

There is no known exploitation of GHSA-3j63-5h8p-gf7c in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-3j63-5h8p-gf7c and fix it if it is affected.

What it is: GHSA-3j63-5h8p-gf7c is a vulnerability in x402, published on 20 Aug 2025. It can be exploited over the network.
Exploitation: There is no known exploitation of GHSA-3j63-5h8p-gf7c in the wild and no public exploit code.

Affected packages and fixed versions:
- x402 (npm): affected all versions; fixed in 0.5.2
- x402 (npm): affected all versions; fixed in 0.5.2
- x402-express (npm): affected all versions; fixed in 0.5.2
- x402-express (npm): affected all versions; fixed in 0.5.2
- x402-hono (npm): affected all versions; fixed in 0.5.2
- x402-hono (npm): affected all versions; fixed in 0.5.2
- x402-next (npm): affected all versions; fixed in 0.5.2
- x402-next (npm): affected all versions; fixed in 0.5.2

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-3j63-5h8p-gf7c/ (Markdown: https://insights.sbomify.com/GHSA-3j63-5h8p-gf7c/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-3j63-5h8p-gf7c

---
From sbomify Insights: https://insights.sbomify.com/GHSA-3j63-5h8p-gf7c/
Summaries are generated and may contain mistakes; the official description above is the record.