{"answers":{"affected":"5 open source packages ship an affected version, including datasette.","exploited":"There is no known exploitation of CVE-2025-64481 in the wild and no public exploit code.","fix":"Upgrade datasette to a fixed version for your release line: 0.65.2 or 1.0a21.","what":"CVE-2025-64481 is a low-severity vulnerability in simonw datasette, published on 7 Nov 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-64481 and fix it if it is affected.\n\nWhat it is: CVE-2025-64481 is a low-severity vulnerability in simonw datasette, published on 7 Nov 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-64481 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- datasette (PyPI): affected all versions; no fix listed\n- datasette (PyPI): affected all versions; fixed in 0.65.2\n- datasette (PyPI): affected all versions; fixed in 0.65.2\n- datasette (PyPI): affected from 1.0a0; fixed in 1.0a21\n- datasette (PyPI): affected from 1.0a0; fixed in 1.0a21\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-64481/ (Markdown: https://insights.sbomify.com/CVE-2025-64481/index.md)","id":"CVE-2025-64481","markdown":"https://insights.sbomify.com/CVE-2025-64481/index.md","name":"CVE-2025-64481","record":{"aliases":["GHSA-w832-gg5g-x44m","PYSEC-2025-73"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Datasette data tool","requires_auth":"none","summary":"Attackers can redirect users to malicious sites via crafted URLs in Datasette, potentially facilitating phishing attacks.","user_interaction":"not_required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.7,"severity":"low","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/E:U","version":"4.0"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"Datasette is an open source multi-tool for exploring and publishing data. In versions 0.65.1 and below and 1.0a0 through 1.0a19, deployed instances of Datasette include an open redirect vulnerability. Hits to the path //example.com/foo/bar/ (the trailing slash is required) will redirect the user to https://example.com/foo/bar. This problem has been patched in both Datasette 0.65.2 and 1.0a21. To workaround this issue, if Datasette is running behind a proxy, that proxy could be configured to replace // with / in incoming request URLs.","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":"Open redirect endpoint in Datasette","id":"CVE-2025-64481","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"open_redirect","year":"2025"},"n_packages":5,"n_references":3,"next":{"headline":"Tuleap missing CSRF protections in the File Release System","id":"CVE-2025-64482"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":[],"last_affected":[],"package":"datasette","purl":"pkg:pypi/datasette","source":"PYSEC-2025-73"},{"ecosystem":"PyPI","fixed":["0.65.2"],"introduced":["0"],"last_affected":[],"package":"datasette","purl":null,"source":"GHSA-w832-gg5g-x44m"},{"ecosystem":"PyPI","fixed":["0.65.2"],"introduced":["0"],"last_affected":[],"package":"datasette","purl":"pkg:pypi/datasette","source":"GHSA-w832-gg5g-x44m"},{"ecosystem":"PyPI","fixed":["1.0a21"],"introduced":["1.0a0"],"last_affected":[],"package":"datasette","purl":null,"source":"GHSA-w832-gg5g-x44m"},{"ecosystem":"PyPI","fixed":["1.0a21"],"introduced":["1.0a0"],"last_affected":[],"package":"datasette","purl":"pkg:pypi/datasette","source":"GHSA-w832-gg5g-x44m"}],"prev":{"headline":"Not used","id":"CVE-2025-64480"},"products":["datasette"],"published":"2025-11-07","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-26","vendors":["simonw"]},"summary":"Attackers can redirect users to malicious sites via crafted URLs in Datasette, potentially facilitating phishing attacks.","url":"https://insights.sbomify.com/CVE-2025-64481/"}