{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-46834 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-46834 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-46834 is a medium-severity authentication bypass vulnerability in alchemyplatform modular-account, published on 15 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-46834 and fix it if it is affected.\n\nWhat it is: CVE-2025-46834 is a medium-severity authentication bypass vulnerability in alchemyplatform modular-account, published on 15 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-46834 in the wild and no public exploit code.\n\nAffected product: alchemyplatform modular-account. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-46834/ (Markdown: https://insights.sbomify.com/CVE-2025-46834/index.md)","id":"CVE-2025-46834","markdown":"https://insights.sbomify.com/CVE-2025-46834/index.md","name":"CVE-2025-46834","record":{"aliases":["GHSA-jhp7-7cq9-m4pv"],"analysis":{"component_type":"other","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Smart contract account","requires_auth":"none","summary":"Session keys can bypass allowlist restrictions to transfer tokens or modify permissions in Alchemy's Modular Account smart contract.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"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` -\u003e `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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Alchemy's Modular Account can use executeUserOp to bypass allowlist prevalidation hook","id":"CVE-2025-46834","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Git GUI can create and overwrite files for which the user has write permission","id":"CVE-2025-46835"},"packages":[],"prev":{"headline":"Programs/P73_SimplePythonEncryption.py has weak cryptographic key","id":"CVE-2025-46833"},"products":["modular-account"],"published":"2025-05-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-19","vendors":["alchemyplatform"]},"summary":"Session keys can bypass allowlist restrictions to transfer tokens or modify permissions in Alchemy's Modular Account smart contract.","url":"https://insights.sbomify.com/CVE-2025-46834/"}