How severe is GHSA-74hv-qjjq-h7g5?

No CVSS score has been assigned to GHSA-74hv-qjjq-h7g5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-74hv-qjjq-h7g5?

GHSA-74hv-qjjq-h7g5 affects the following packages: datasette-graphql (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-74hv-qjjq-h7g5?

Update datasette-graphql to 1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-74hv-qjjq-h7g5 is resolved across your whole dependency graph.

How do I detect GHSA-74hv-qjjq-h7g5 in my PyPI dependencies?

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

How do I mitigate GHSA-74hv-qjjq-h7g5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-74hv-qjjq-h7g5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-74hv-qjjq-h7g5 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.

When was GHSA-74hv-qjjq-h7g5 published, and has it been updated?

GHSA-74hv-qjjq-h7g5 was published on November 24, 2020 and was last updated on December 2, 2024. 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

datasette-graphql leaks details of the schema of private database filesGHSA-74hv-qjjq-h7g5

GHSA-74hv-qjjq-h7g5 is a security vulnerability in datasette-graphql. A fix is available for datasette-graphql — see the affected versions and patch details below.

Published

Nov 24, 2020

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍datasette-graphql

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

Impact

When running against a Datasette instance with private databases, datasette-graphql would expose the schema of those database tables - but not the table contents.

Patches

Patched in version 1.2.

Workarounds

This issue is only present if a Datasette instance that includes private databases and has the datasette-graphql plugin installed is available on the public internet. Uninstalling the datasette-graphql plugin or preventing public access to the instance can workaround this issue.

For more information

If you have any questions or comments about this advisory:

Open an issue in datasette-graphql
Contact @simonw by Twitter direct message

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`datasette-graphql`	all versions	1.2`pip install --upgrade 'datasette-graphql==1.2'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for datasette-graphql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update datasette-graphql to 1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-74hv-qjjq-h7g5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact When running against a Datasette instance with private databases, `datasette-graphql` would expose the schema of those database tables - but not the table contents. ### Patches Patched in version 1.2. ### Workarounds This issue is only present if a Datasette instance that includes private databases and has the `datasette-graphql` plugin installed is available on the public internet. Uninstalling the `datasette-graphql` plugin or preventing public access to the instance can workaround this issue. ### For more information If you have any questions or comments about this advisory

O3 Security · Impact-Aware SCA

Is GHSA-74hv-qjjq-h7g5 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

datasette-graphql leaks details of the schema of private database filesGHSA-74hv-qjjq-h7g5

Real-World Exposure

Description

Impact

Patches

Workarounds

For more information

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-74hv-qjjq-h7g5 in your dependencies?