# CVE-2026-105652: Ghost: Password Hash Ordering Disclosure in Ghost Admin API

> Staff users can determine the relative ordering of other staff users' hashed passwords, leaking metadata about password hashes.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** MINI-v6mc-6q64-7mq6

## What is CVE-2026-105652?

CVE-2026-105652 is a low-severity vulnerability in TryGhost Ghost, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Ghost is a Node.js content management system. From 0.7.2 until 6.64.0, any staff-level user was able to determine the relative ordering of other staff users' hashed passwords. This does not directly disclose password hashes, and does not provide a practical path to recovering a password. This issue is fixed in version 6.64.0.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic), CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2026-105652?


## How do I fix CVE-2026-105652?

Upgrade to a fixed version.

## Is CVE-2026-105652 being exploited?

There is no known exploitation of CVE-2026-105652 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105652 and fix it if it is affected.

What it is: CVE-2026-105652 is a low-severity vulnerability in TryGhost Ghost, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105652 in the wild and no public exploit code.

Affected product: TryGhost Ghost. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105652/ (Markdown: https://insights.sbomify.com/CVE-2026-105652/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105652
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105652
- OSV: https://osv.dev/vulnerability/CVE-2026-105652

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105652/
Summaries are generated and may contain mistakes; the official description above is the record.