How severe is CVE-2026-53471?

CVE-2026-53471 has a CVSS 3.x base score of 9.6, rated critical severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2026-53471 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-53471?

CVE-2026-53471 affects Kebev2v Migration Assessment. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-53471?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2026-53471 have an EU (EUVD) identifier?

Yes. CVE-2026-53471 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-36031.

When was CVE-2026-53471 published?

CVE-2026-53471 was published on 2026-06-10 and last updated on 2026-06-17.

CVE-2026-53471

CVE-2026-53471 is a critical-severity vulnerability in Kebev2v Migration Assessment with a CVSS 3.x base score of 9.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-639.

Key facts

Severity: Critical (CVSS 3.x base score 9.6)
EPSS exploit prediction: 0% (20th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-36031
Weakness: CWE-639
Affected product: Kebev2v Migration Assessment
Published: 2026-06-10
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2026-53471?: 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.
How severe is CVE-2026-53471?: CVE-2026-53471 has a CVSS 3.x base score of 9.6, rated critical severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2026-53471 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-53471?: CVE-2026-53471 affects Kebev2v Migration Assessment. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-53471?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2026-53471 have an EU (EUVD) identifier?: Yes. CVE-2026-53471 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-36031.
When was CVE-2026-53471 published?: CVE-2026-53471 was published on 2026-06-10 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:kebev2v:migration_assessment:*:*:*:*:*:*:*:*

More vulnerabilities in Kebev2v Migration Assessment

CVE-2026-53474 — Critical (CVSS 9.6): A flaw was found in migration-planner. A remote authenticated attacker could exploit this vulnerability by uploading a…
CVE-2026-53470 — Critical (CVSS 9.6): A flaw was found in migration-planner. An authenticated attacker could exploit an improper access control vulnerability…
CVE-2026-53469 — Critical (CVSS 9.1): A flaw was found in migration-planner. An authenticated user can exploit this vulnerability by sending a DELETE request…

All CVEs affecting Kebev2v Migration Assessment →

Other CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities

CVE-2025-40805 — Critical (CVSS 10.0): Affected devices do not properly enforce user authentication on specific API endpoints. This could facilitate an…
CVE-2024-45032 — Critical (CVSS 10.0): A vulnerability has been identified in Industrial Edge Management Pro (All versions < V1.9.5), Industrial Edge…
CVE-2026-34037 — Critical (CVSS 9.9): Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to…
CVE-2026-52782 — Critical (CVSS 9.9): OpenProject is open-source, web-based project management software. Prior to 17.3.3 and 17.4.1, there is an IDOR through…
CVE-2026-45552 — Critical (CVSS 9.9): Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepalived servers. In versions 8.2.6.4 and prior,…
CVE-2026-29200 — Critical (CVSS 9.9): A critical IDOR vulnerability has been discovered in Comet Backup affecting all versions from 20.11.0 to 26.1.1 and…

Browse all CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities →