# GHSA-56r6-ccm5-8hg3: Alchemy Non-SMA and Webauthn Account Security Advisory

> Old Alchemy account deployment functions had a security issue mitigated by using new factory methods for smart wallet creation.

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

## What is GHSA-56r6-ccm5-8hg3?

GHSA-56r6-ccm5-8hg3 is a vulnerability in @account-kit/smart-contracts, published on 21 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Impact
A potential security issue has been mitigated on old account deployment functions from the factory. Smart wallets in use on all existing supported networks are not impacted.
### Patches
Please direct creation of new wallets to either `createSemiModularAccount` on `AccountFactory.sol` or `createWebAuthnAccount` on `WebAuthnFactory.sol`.

## Which versions are affected by GHSA-56r6-ccm5-8hg3?

2 open source packages ship an affected version, including @account-kit/smart-contracts.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@account-kit/smart-contracts` | npm | From 4.42.0 | 4.52.0 |
| `@account-kit/smart-contracts` | npm | From 4.42.0 | 4.52.0 |

## How do I fix GHSA-56r6-ccm5-8hg3?

Upgrade @account-kit/smart-contracts to 4.52.0 or later.

## Is GHSA-56r6-ccm5-8hg3 being exploited?

There is no known exploitation of GHSA-56r6-ccm5-8hg3 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-56r6-ccm5-8hg3 and fix it if it is affected.

What it is: GHSA-56r6-ccm5-8hg3 is a vulnerability in @account-kit/smart-contracts, published on 21 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-56r6-ccm5-8hg3 in the wild and no public exploit code.

Affected packages and fixed versions:
- @account-kit/smart-contracts (npm): affected from 4.42.0; fixed in 4.52.0
- @account-kit/smart-contracts (npm): affected from 4.42.0; fixed in 4.52.0

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-56r6-ccm5-8hg3/ (Markdown: https://insights.sbomify.com/GHSA-56r6-ccm5-8hg3/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-56r6-ccm5-8hg3

---
From sbomify Insights: https://insights.sbomify.com/GHSA-56r6-ccm5-8hg3/
Summaries are generated and may contain mistakes; the official description above is the record.