# CVE-2026-53471: Migration-planner: agent api ignores jwt source_id claim

> Authenticated attackers can bypass tenant isolation in migration-planner to modify other tenants' inventory and assessments due to missing JWT claim validation.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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:** 10 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** GHSA-2fqw-7c6r-2cq6, GO-2026-6228

## What is CVE-2026-53471?

CVE-2026-53471 is a critical missing authorization vulnerability in kebev2v:migration_assessment, published on 10 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in migration-planner. The agent-API middleware processes JSON Web Tokens (JWTs) for authentication, but its UpdateSourceInventory and UpdateAgentStatus handlers fail to validate the source_id claim within these tokens against the requested source ID. This oversight allows an authenticated attacker with a valid agent token to manipulate data across different tenants, leading to a complete collapse of tenant isolation. This could result in unauthorized overwriting of victim inventory, planting of malicious credential URLs, or corruption of migration assessments.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

3 open source packages ship an affected version, including github.com/kubev2v/migration-planner. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/kubev2v/migration-planner` | Go | All versions | 0.13.5 |
| `github.com/kubev2v/migration-planner` | Go | All versions | 0.13.5 |
| `github.com/kubev2v/migration-planner` | Go | All versions | 0.13.5 |

Products: Kebev2v Migration Assessment.

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

Upgrade github.com/kubev2v/migration-planner to 0.13.5 or later.

## Is CVE-2026-53471 being exploited?

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

## Other vulnerabilities in kebev2v:migration_assessment

- [CVE-2026-53470](https://insights.sbomify.com/CVE-2026-53470/): Migration-planner: getsourcedownloadurl missing organization check (critical 9.6)
- [CVE-2026-53474](https://insights.sbomify.com/CVE-2026-53474/): Migration-planner: second-order sql injection via rvtools upload (critical 9.6)
- [CVE-2026-53469](https://insights.sbomify.com/CVE-2026-53469/): Migration-planner: unprotected delete endpoint wipes all tenant data (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53471 is a critical missing authorization vulnerability in kebev2v:migration_assessment, published on 10 Jun 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-53471 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/kubev2v/migration-planner (Go): affected all versions; fixed in 0.13.5
- github.com/kubev2v/migration-planner (Go): affected all versions; fixed in 0.13.5
- github.com/kubev2v/migration-planner (Go): affected all versions; fixed in 0.13.5

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-53471/ (Markdown: https://insights.sbomify.com/CVE-2026-53471/index.md)
```

## Sources

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

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