How severe is GHSA-56r6-ccm5-8hg3?

No CVSS score has been assigned to GHSA-56r6-ccm5-8hg3 yet. Review the advisory details and affected package list to assess your exposure.

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

GHSA-56r6-ccm5-8hg3 affects the following packages: @account-kit/smart-contracts (npm). Ecosystems affected: npm.

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

Update @account-kit/smart-contracts to 4.52.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-56r6-ccm5-8hg3 is resolved across your whole dependency graph.

How do I detect GHSA-56r6-ccm5-8hg3 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @account-kit/smart-contracts. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-56r6-ccm5-8hg3 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-56r6-ccm5-8hg3?

O3 pinpoints whether GHSA-56r6-ccm5-8hg3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-56r6-ccm5-8hg3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-56r6-ccm5-8hg3 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-56r6-ccm5-8hg3 published, and has it been updated?

GHSA-56r6-ccm5-8hg3 was published on July 21, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-56r6-ccm5-8hg3: Alchemy Non-SMA and Webauthn Account Secur…

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

@account-kit/smart-contractsnpm

28Kdownloads / week

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@account-kit/smart-contracts`	≥ 4.42.0&&< 4.52.0	4.52.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @account-kit/smart-contracts. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @account-kit/smart-contracts to 4.52.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-56r6-ccm5-8hg3 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 pinpoints whether GHSA-56r6-ccm5-8hg3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-56r6-ccm5-8hg3. 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 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`.

O3 Security · Impact-Aware SCA

Is GHSA-56r6-ccm5-8hg3 in your dependencies?

O3 detects GHSA-56r6-ccm5-8hg3 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-56r6-ccm5-8hg3