CVE-2025-46834

Source
https://nvd.nist.gov/vuln/detail/CVE-2025-46834
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-46834.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2025-46834
Aliases
  • GHSA-jhp7-7cq9-m4pv
Published
2025-05-15T20:16:08Z
Modified
2025-05-17T14:29:18.254585Z
Summary
[none]
Details

Alchemy's Modular Account is a smart contract account that is compatible with ERC-4337 and ERC-6900. In versions on the 2.x branch prior to commit 5e6f540d249afcaeaf76ab95517d0359fde883b0, owners of Modular Accounts can grant session keys (scoped external keys) to external parties and would use the allowlist module to restrict which external contracts can be accessed by the session key. There is a bug in the allowlist module in that we don't check for the executeUserOp -> execute or executeBatch path, effectively allowing any session key to bypass any access control restrictions set on the session key. Session keys are able to access ERC20 and ERC721 token contracts amongst others, transferring all tokens from the account out andonfigure the permissions on external modules on session keys. They would be able to remove all restrictions set on themselves this way, or rotate the keys of other keys with higher privileges into keys that they control. Commit 5e6f540d249afcaeaf76ab95517d0359fde883b0 fixes this issue.

References

Affected packages

Git / github.com/alchemyplatform/modular-account

Affected ranges

Type
GIT
Repo
https://github.com/alchemyplatform/modular-account
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed

Affected versions

v1.*

v1.0.0
v1.0.0-alpha.0
v1.0.1-npm

v2.*

v2.0.0