CVE-2025-64481VulnerabilityPublished 7 Nov 2025Updated 26 Dec 2025

CVE-2025-64481: simonw datasette · Open Redirect

Affects simonw datasetteSource CVE Database V5

Not known to be exploited · CVSS 2.7 Low : upgrade to 0.65.2 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

2.7Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.65.2

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: Unreported

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: Unreported: Based on threat intelligence sources each of the following must apply: · No knowledge of publicly available proof-of-concept · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade simonw datasette to 0.65.2.

Affected software

Product	Affected	Fixed in
PyPIdatasette`pkg:pypi/datasette`Other threats	Affected <0.65.2	Fixed in 0.65.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade all Datasette deployments to version 0.65.2 or later, or 1.0a21 or later, where the vulnerability is patched. 2. For environments where immediate upgrade is not feasible, configure reverse proxies (e.g., Nginx, Apache, HAProxy) to normalize incoming URLs by replacing occurrences of double slashes (//) in the path with a single slash (/). This prevents the open redirect trigger. 3. Implement strict URL validation and sanitization on any user-facing links generated by Datasette or related applications to avoid embedding untrusted redirects. 4. Educate users and administrators about the risk of open redirects and encourage vigilance against suspicious URLs, especially those containing unusual double slashes. 5. Monitor web server and proxy logs for unusual redirect patterns or requests containing double slashes in URLs. 6. Consider deploying web application firewalls (WAFs) with custom rules to detect and block requests attempting to exploit this redirect behavior. 7. Review and update organizational phishing awareness programs to include risks associated with open redirect vulnerabilities. 8. For public-facing Datasette instances, consider implementing Content Security Policy (CSP) headers to restrict navigation to trusted domains, mitigating the impact of malicious redirects.

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.

Impact

For European organizations, the primary risk posed by CVE-2025-64481 is the potential for phishing and social engineering attacks leveraging trusted Datasette URLs that redirect users to malicious sites. This could undermine user trust in published data portals and expose end users to credential theft or malware delivery. However, the vulnerability does not directly compromise the confidentiality, integrity, or availability of the Datasette service or the underlying data. Organizations using Datasette for public data publication or internal data sharing may face reputational damage if users are redirected to harmful sites. The impact is more pronounced in sectors with high reliance on data transparency and public engagement, such as government open data initiatives, research institutions, and NGOs. Since exploitation requires no authentication and no user interaction beyond clicking a crafted link, attackers could distribute malicious URLs via email or social media. Nonetheless, the low CVSS score and absence of known exploits suggest limited immediate risk. Prompt patching or proxy-based mitigation will effectively reduce exposure. Overall, the impact on European organizations is low but non-negligible, especially for those with public-facing Datasette instances.

Summary

CVE-2025-64481 is classified as a CWE-601 open redirect vulnerability found in the Datasette tool, an open source platform widely used for exploring and publishing data. The vulnerability exists in Datasette versions prior to 0.65.2 and between 1.0a0 and 1.0a19 inclusive. It arises from improper handling of URLs containing double slashes (//) in the path component. Specifically, when a URL path includes a double slash followed by a domain-like string (e.g., //example.com/foo/bar/), Datasette interprets this as a redirect instruction, sending users to the external site https://example.com/foo/bar. This behavior can be exploited by attackers to craft malicious links that redirect users to untrusted or harmful websites, potentially facilitating phishing attacks or other social engineering exploits. The vulnerability does not require authentication or user interaction to be triggered, but the impact is limited to redirecting users, without direct compromise of confidentiality, integrity, or availability of the Datasette server or data. The issue has been addressed in Datasette versions 0.65.2 and 1.0a21 by correcting URL parsing logic to prevent open redirects. As an interim mitigation, organizations deploying Datasette behind reverse proxies can configure those proxies to rewrite incoming URLs by replacing double slashes with a single slash, thus neutralizing the redirect vector. No known exploits have been reported in the wild as of the publication date. The CVSS 4.0 base score is 2.7, reflecting low severity due to the limited scope and impact of the vulnerability.

CWE-601URL Redirection to Untrusted Site ('Open Redirect') (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
Use an intermediate disclaimer page that provides the user with a clear warning that they are leaving the current site. Implement a long timeout before the redirect occurs, or force the user to click on the link. Be careful to avoid XSS problems (CWE-79) when generating the disclaimer page.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
OWASP Cheat Sheets
Mass Assignment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V5.1.5 (opens in a new tab)
Attack patterns
Cross-Site Flashing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Dec 2025, 22:25 UTC

WeaknessesCWE-601

Technical details

References

Community reviews

Related threats