# CVE-2026-105445: Docker Hub account conversion could reassign an active personal access token to another user

> An attacker can reassign their personal access token to another user, gaining unauthorized access to pull, push, or delete images in that user's repositories.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-phq5-vq2m-8rp9

## What is CVE-2026-105445?

CVE-2026-105445 is a critical vulnerability in Docker Hub, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An Incorrect Privilege Assignment vulnerability in Docker Hub's account-to-organization conversion feature allowed an authenticated attacker to reassign a personal access token (PAT) they controlled to another Docker Hub user without rotating or revoking the token secret. The unchanged PAT then authenticated to the registry as the recipient and could pull, push, or delete images, within its scopes, in repositories accessible to that user, including organization repositories.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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


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

No fix has been published for CVE-2026-105445 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105445 being exploited?

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

Public exploit code:

- Offline Docker Hub PAT evidence checker for CVE-2026-105445. Supplied evidence only; no token collection, login or API requests. JSON/CSV/HTML reports. (github_poc): https://github.com/CompleteTech-Security/docker-hub-ghostpat-check

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105445 is a critical vulnerability in Docker Hub, published on 13 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-105445 in the wild and no public exploit code.

Affected product: Docker Hub. 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-105445/ (Markdown: https://insights.sbomify.com/CVE-2026-105445/index.md)
```

## Sources

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

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