{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40072 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-40072 is a low-severity server-side request forgery vulnerability in ethereum web3.py, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-40072 and fix it if it is affected.\n\nWhat it is: CVE-2026-40072 is a low-severity server-side request forgery vulnerability in ethereum web3.py, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40072 exists.\n\nAffected product: ethereum web3.py. 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-2026-40072/ (Markdown: https://insights.sbomify.com/CVE-2026-40072/index.md)","id":"CVE-2026-40072","markdown":"https://insights.sbomify.com/CVE-2026-40072/index.md","name":"CVE-2026-40072","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python blockchain library","requires_auth":"none","summary":"Malicious smart contracts can force web3.py to send HTTP requests to arbitrary internal or external URLs, enabling Server-Side Request Forgery attacks.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"web3.py","vendor":"apeworx"}],"cvss":{"score":1.7,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"web3.py allows you to interact with the Ethereum blockchain using Python. From 6.0.0b3 to before 7.15.0 and 8.0.0b2, web3.py implements CCIP Read / OffchainLookup (EIP-3668) by performing HTTP requests to URLs supplied by smart contracts in offchain_lookup_payload[\"urls\"]. The implementation uses these contract-supplied URLs directly (after {sender} / {data} template substitution) without any destination validation. CCIP Read is enabled by default (global_ccip_read_enabled = True on all providers), meaning any application using web3.py's .call() method is exposed without explicit opt-in. This results in Server-Side Request Forgery (SSRF) when web3.py is used in backend services, indexers, APIs, or any environment that performs eth_call / .call() against untrusted or user-supplied contract addresses. A malicious contract can force the web3.py process to issue HTTP requests to arbitrary destinations, including internal network services and cloud metadata endpoints. This vulnerability is fixed in 7.15.0 and 8.0.0b2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-06-05","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-06-05T09:05:30Z","kind":"github_poc","ref":"https://github.com/u1tr0nex/cve-2026-40072-ssrf-lab","stars":0,"title":"Hands-on lab for CVE-2026-40072 — SSRF vulnerability in web3.py via CCIP Read (EIP-3668)"}],"tier":"weaponised"},"has_fix":true,"headline":"web3.py affected by SSRF via CCIP Read (EIP-3668) OffchainLookup URL handling","id":"CVE-2026-40072","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"SvelteKit has a BODY_SIZE_LIMIT bypass in @sveltejs/adapter-node","id":"CVE-2026-40073"},"packages":[],"prev":{"headline":"pyLoad WebUI JSON permission mismatch lets ADD/DELETE users invoke MODIFY-only actions","id":"CVE-2026-40071"},"products":["web3.py"],"published":"2026-04-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-09","vendors":["ethereum"]},"summary":"Malicious smart contracts can force web3.py to send HTTP requests to arbitrary internal or external URLs, enabling Server-Side Request Forgery attacks.","url":"https://insights.sbomify.com/CVE-2026-40072/"}