Bug 2487070 (CVE-2026-53471) - CVE-2026-53471 migration-planner: Agent API Ignores JWT source_id Claim
Summary: CVE-2026-53471 migration-planner: Agent API Ignores JWT source_id Claim
Keywords:
Status: NEW
Alias: CVE-2026-53471
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-09 17:49 UTC by OSIDB Bzimport
Modified: 2026-06-10 13:53 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-06-09 17:49:14 UTC
Repository: migration-planner  
Priority: High  
Location: internal/handlers/v1alpha1/agent.go:39

Description:  
Each agent OVA carries a JWT with a source_id claim identifying the single source it should manage. The agent-API middleware validates the JWT signature and stores claims in context, but UpdateSourceInventory and UpdateAgentStatus handlers never check these claims. They trust the source ID from the URL path/request body instead. Helper functions auth.AgentFromContext / MustHaveAgent exist but have zero call sites.

Security Impact:  

Complete tenant isolation collapse on agent surface

Any valid agent token grants write capability for every tenant's source

Attacker can overwrite victim inventory, plant malicious credentialUrl, or corrupt migration assessments

Chains with f003 for full cross-tenant write from any Hybrid Cloud Console  login

Fix Suggestion:  
Read auth.MustHaveAgent(ctx).SourceID in both handlers and return 403 when it doesn't match the target source. The 403 response types already exist in generated server code. See patches/f002.patch.


Note You need to log in before you can comment on or make changes to this bug.