{"answers":{"affected":"2 open source packages ship an affected version, including @account-kit/smart-contracts.","exploited":"There is no known exploitation of GHSA-wfm2-rq5g-f8v5 in the wild and no public exploit code.","fix":"Upgrade @account-kit/smart-contracts to 4.28.2 or later.","what":"GHSA-wfm2-rq5g-f8v5 is a vulnerability in @account-kit/smart-contracts, published on 29 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-wfm2-rq5g-f8v5 and fix it if it is affected.\n\nWhat it is: GHSA-wfm2-rq5g-f8v5 is a vulnerability in @account-kit/smart-contracts, published on 29 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-wfm2-rq5g-f8v5 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @account-kit/smart-contracts (npm): affected from 4.8.0; fixed in 4.28.2\n- @account-kit/smart-contracts (npm): affected from 4.8.0; fixed in 4.28.2\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/GHSA-wfm2-rq5g-f8v5/ (Markdown: https://insights.sbomify.com/GHSA-wfm2-rq5g-f8v5/index.md)","id":"GHSA-wfm2-rq5g-f8v5","markdown":"https://insights.sbomify.com/GHSA-wfm2-rq5g-f8v5/index.md","name":"GHSA-wfm2-rq5g-f8v5","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Smart contract library","requires_auth":"low_privilege","summary":"Session keys can bypass allowlist configurations in Modular Account V2, allowing unauthorized actions if specific versions are used.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Summary\nAllowlist module contains a bypass vulnerability\n\n### Details\nThe logic for using an allowlist on a Modular Account V2 contained a bug that allowed session keys to bypass any allowlist configuration\n\n### Action\nIf you are using @aa-sdk and/or @account-kit/smart-contracts between the versions of \u003e=4.8.0 and \u003c4.28.1, please upgrade to 4.28.2","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"@account-kit/smart-contracts Allowlist Module Bypass Vulnerability","id":"GHSA-wfm2-rq5g-f8v5","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["4.28.2"],"introduced":["4.8.0"],"last_affected":[],"package":"@account-kit/smart-contracts","purl":null,"source":"GHSA-wfm2-rq5g-f8v5"},{"ecosystem":"npm","fixed":["4.28.2"],"introduced":["4.8.0"],"last_affected":[],"package":"@account-kit/smart-contracts","purl":"pkg:npm/%40account-kit/smart-contracts","source":"GHSA-wfm2-rq5g-f8v5"}],"products":null,"published":"2025-04-29","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Session keys can bypass allowlist configurations in Modular Account V2, allowing unauthorized actions if specific versions are used.","url":"https://insights.sbomify.com/GHSA-wfm2-rq5g-f8v5/"}