{"answers":{"affected":"3 open source packages ship an affected version, including crawlee.","exploited":"There is no known exploitation of CVE-2026-46497 in the wild and no public exploit code.","fix":"Upgrade crawlee to 1.7.0 or later.","what":"CVE-2026-46497 is a low-severity server-side request forgery vulnerability in apify crawlee-python, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-46497 and fix it if it is affected.\n\nWhat it is: CVE-2026-46497 is a low-severity server-side request forgery vulnerability in apify crawlee-python, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-46497 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- crawlee (PyPI): affected from 1.0.0; fixed in 1.7.0\n- crawlee (PyPI): affected from 1.0.0; fixed in 1.7.0\n- crawlee (PyPI): affected from 1.0.0; fixed in 1.7.0\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-46497/ (Markdown: https://insights.sbomify.com/CVE-2026-46497/index.md)","id":"CVE-2026-46497","markdown":"https://insights.sbomify.com/CVE-2026-46497/index.md","name":"CVE-2026-46497","record":{"aliases":["GHSA-3r75-xc34-5f44","PYSEC-2026-2430"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python web scraping library","requires_auth":"none","summary":"Attackers can exploit SSRF in Crawlee for Python via sitemap-derived URLs to access internal resources or bypass security controls.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Crawlee is a web scraping and browser automation library. From version 1.0.0 to before version 1.7.0, Crawlee is vulnerable to SSRF via sitemap-derived URLs. This issue has been patched in version 1.7.0.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"SSRF via sitemap-derived URLs in Crawlee for Python","id":"CVE-2026-46497","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"OpenAM Arbitrary OAuth Token Minting via Push Registration","id":"CVE-2026-46498"},"packages":[{"ecosystem":"PyPI","fixed":["1.7.0"],"introduced":["1.0.0"],"last_affected":[],"package":"crawlee","purl":null,"source":"GHSA-3r75-xc34-5f44"},{"ecosystem":"PyPI","fixed":["1.7.0"],"introduced":["1.0.0"],"last_affected":[],"package":"crawlee","purl":"pkg:pypi/crawlee","source":"GHSA-3r75-xc34-5f44"},{"ecosystem":"PyPI","fixed":["1.7.0"],"introduced":["1.0.0"],"last_affected":[],"package":"crawlee","purl":"pkg:pypi/crawlee","source":"PYSEC-2026-2430"}],"prev":{"headline":"HAX CMS: Stored XSS via '\u003cvideo-player\u003e' component allows arbitrary JavaScript execution and token theft","id":"CVE-2026-46496"},"products":["crawlee-python"],"published":"2026-06-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"2026-06-10","vendors":["apify"]},"summary":"Attackers can exploit SSRF in Crawlee for Python via sitemap-derived URLs to access internal resources or bypass security controls.","url":"https://insights.sbomify.com/CVE-2026-46497/"}