{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-53638 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-53638 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-53638 is a medium-severity vulnerability in Vectorized solady, published on 17 Jul 2025."},"fix_prompt":"Check this codebase for CVE-2025-53638 and fix it if it is affected.\n\nWhat it is: CVE-2025-53638 is a medium-severity vulnerability in Vectorized solady, published on 17 Jul 2025. \nExploitation: There is no known exploitation of CVE-2025-53638 in the wild and no public exploit code.\n\nAffected product: Vectorized solady. 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-53638/ (Markdown: https://insights.sbomify.com/CVE-2025-53638/index.md)","id":"CVE-2025-53638","markdown":"https://insights.sbomify.com/CVE-2025-53638/index.md","name":"CVE-2025-53638","record":{"aliases":["GHSA-8xvx-4mvg-m9v8"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"}],"description":"Solady is software that provides Solidity snippets with APIs. Starting in version 0.0.125 and prior to version 0.1.24, when an account is deployed via a proxy, using regular Solidity to call its initialization function may result in a silent failure, if the initialization function does not return a `bool` or some other return data.  This is because regular Solidity uses `extcodesize(proxy)` to decide if call succeeds. This is insufficient in the case when the proxy points to an empty implementation. Users should upgrade to Solady v0.1.24 or later to receive a patch. Deploy any affected implementations and their factories on new EVM chains as soon as possible.","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":"Solady lacks extcodesize validation on implementation in ERC4337Factory","id":"CVE-2025-53638","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Metersphere has SQL Injection Vulnerability in Sorting Field","id":"CVE-2025-53639"},"packages":[],"prev":{"headline":"Meshtastic allows Command Injection in GitHub Action","id":"CVE-2025-53637"},"products":["solady"],"published":"2025-07-17","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-17","vendors":["Vectorized"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-53638/"}