How severe is GHSA-chgm-3698-jm42?

GHSA-chgm-3698-jm42 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-chgm-3698-jm42?

GHSA-chgm-3698-jm42 affects the following packages: ghost (npm). Ecosystems affected: npm.

How do I fix GHSA-chgm-3698-jm42?

Update ghost to 6.21.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-chgm-3698-jm42 is resolved across your whole dependency graph.

How do I detect GHSA-chgm-3698-jm42 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ghost. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-chgm-3698-jm42 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.

How does O3 Security protect against GHSA-chgm-3698-jm42?

O3 pinpoints whether GHSA-chgm-3698-jm42 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-chgm-3698-jm42 actively exploited in the wild?

No public exploit code has been indexed for GHSA-chgm-3698-jm42 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 type of vulnerability is GHSA-chgm-3698-jm42?

GHSA-chgm-3698-jm42 is classified as CWE-204 (CWE-204). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-chgm-3698-jm42 published, and has it been updated?

GHSA-chgm-3698-jm42 was published on August 4, 2026 and was last updated on August 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-chgm-3698-jm42

MEDIUM

GHSA-chgm-3698-jm42 is a medium-severity (CVSS 5.3) CWE-204 vulnerability in ghost. O3 Security confirms whether GHSA-chgm-3698-jm42 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Ghost: Member existence leak via magic link sign-in response

Also known asBIT-ghost-2026-53947CVE-2026-53947

Published

Aug 4, 2026

Updated

Aug 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

📦ghost

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

Description

Impact

A discrepancy in responses from the members signin endpoints made it possible for an unauthenticated attacker to determine whether a given email address belongs to a registered member of a Ghost site.

Vulnerable versions

This vulnerability is present in Ghost from v5.18.0 up to v6.21.0.

Patches

v6.21.1 contains a fix for this issue.

How to update

For self-hosters using Docker, find Docker's official Ghost image here. Updating a Docker-based Ghost instance is documented here.

If your Ghost is a Ghost-CLI install see our documentation on updating it to the latest version here.

For more information

If you have any questions or comments about this advisory, email Ghost at [email protected].

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`ghost`	≥ 5.18.0&&< 6.21.2	6.21.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ghost. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ghost to 6.21.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-chgm-3698-jm42 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.
How O3 protects you
O3 pinpoints whether GHSA-chgm-3698-jm42 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-chgm-3698-jm42. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A discrepancy in responses from the members signin endpoints made it possible for an unauthenticated attacker to determine whether a given email address belongs to a registered member of a Ghost site. ### Vulnerable versions This vulnerability is present in Ghost from v5.18.0 up to v6.21.0. ### Patches v6.21.1 contains a fix for this issue. ### How to update For self-hosters using Docker, find [Docker's official Ghost image here](https://hub.docker.com/_/ghost). Updating a Docker-based Ghost instance [is documented here](https://docs.ghost.org/install/docker#updating-ghost).

O3 Security · Impact-Aware SCA

Is GHSA-chgm-3698-jm42 in your dependencies?

O3 detects GHSA-chgm-3698-jm42 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works