GPU VulnDB

Database/AI/ML frameworks & serving

iFlytek astron-agent: copyFlow lacks an ownership check, letting any tenant read or overwrite workflows

CVE-2026-82475AI/ML frameworks & servingcurated

Impact

astron-agent's copyFlow endpoint does not verify that the caller owns the workflow it names. Any authenticated account can enumerate workflow identifiers and either copy a private workflow to read its full definition or overwrite another tenant's workflow. Workflow definitions are where prompts, model selection, tool and API wiring, and any embedded endpoint configuration live, so reading one exposes another tenant's agent design and whatever credentials-adjacent configuration it carries. Overwriting one changes what actually executes on the fleet's inference capacity under the victim tenant's identity, and the victim gets no signal that their workflow was replaced. On a shared platform this collapses the tenant boundary in both directions with nothing more than a login.

Who can reach it

Any authenticated user of the astron-agent console, including a low-privilege tenant account. No administrative role is needed - the record states privileges are low and the identifiers are enumerable.

What to do

No fixed version exists in this record: the flaw is reported through 1.1.1 and tracked in an open upstream issue. Mitigate rather than patch - restrict console access to trusted operators, put the backend behind an authenticating proxy that scopes workflow identifiers per tenant, and treat any multi-tenant astron-agent deployment as offering no workflow isolation until upstream ships a check. If tenants genuinely do not trust each other, separate them into distinct instances.

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.