How severe is GHSA-w832-gg5g-x44m?

No CVSS score has been assigned to GHSA-w832-gg5g-x44m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w832-gg5g-x44m?

GHSA-w832-gg5g-x44m affects the following packages: datasette (PyPI), datasette (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-w832-gg5g-x44m?

Update datasette to 0.65.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w832-gg5g-x44m is resolved across your whole dependency graph.

How do I detect GHSA-w832-gg5g-x44m in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for datasette, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-w832-gg5g-x44m if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is GHSA-w832-gg5g-x44m actively exploited in the wild?

No public exploit code has been indexed for GHSA-w832-gg5g-x44m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-w832-gg5g-x44m?

GHSA-w832-gg5g-x44m has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 36th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-w832-gg5g-x44m?

GHSA-w832-gg5g-x44m is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-w832-gg5g-x44m published, and has it been updated?

GHSA-w832-gg5g-x44m was published on November 6, 2025 and was last updated on May 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

Open redirect endpoint in DatasetteGHSA-w832-gg5g-x44m

Fix: simonw/datasette@f257ca6

GHSA-w832-gg5g-x44m is a Open Redirect vulnerability in datasette. A fix is available for datasette — see the affected versions and patch details below.

Also known asCVE-2025-64481PYSEC-2025-73

Published

Nov 6, 2025

Updated

May 19, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-w832-gg5g-x44m.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs36th percentile — riskier than 36% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

🐍datasette🐍datasette

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`datasette`	all versions	0.65.2`pip install --upgrade 'datasette==0.65.2'`
🐍PyPI	`datasette`	≥ 1.0a0&&< 1.0a21	1.0a21`pip install --upgrade 'datasette==1.0a21'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for datasette, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update datasette to 0.65.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w832-gg5g-x44m is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Frequently Asked Questions

### Impact Deployed instances of Datasette prior to `0.65.2` and `1.0a21` 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`. ### Patches This problem has been patched in both Datasette `0.65.2` and `1.0a21`. ### Workarounds If Datasette is running behind a proxy that proxy could be configured to replace `//` with `/` in incoming request URLs.

O3 Security · Impact-Aware SCA

Is GHSA-w832-gg5g-x44m in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works