GPU VulnDB

Database/AI/ML frameworks & serving

iFlytek Astron Agent: workflow resume endpoint accepts another application's event_id

CVSS 2.3CVE-2026-108864AI/ML frameworks & servingcurated

Impact

Astron Agent through 1.1.2 does not check that the event_id passed to POST /workflow/v1/resume belongs to the calling application, so an authenticated tenant can resume another tenant's paused workflow. Because the event ids are Snowflake values they are guessable from a known timestamp, which makes this practical rather than theoretical. The attacker both injects the resume content the victim workflow continues on - steering a human-in-the-loop step toward their own input - and reads the victim's continuation output stream, which carries model output derived from the victim's data. On a shared agent platform fronting a GPU fleet this is a direct break of cross-tenant isolation in both directions, affecting data the operator promised to keep separate.

Who can reach it

Network, authenticated as any application on the platform. No admin role and no prior access to the victim application are needed - only a guessed or observed event_id.

What to do

No fixed version is named in the record. Until the vendor publishes one, restrict reachability of /workflow/v1/resume to trusted callers at the gateway and avoid relying on Astron Agent 1.1.2 or earlier for multi-tenant workloads with data separation requirements. Any mitigation here is a gateway or deployment-topology change, not a node-level maintenance action.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.