CVE-2026-116340: iFlytek astron-agent authorization bypass in knowledge-list endpoint

CVE-2026-116340 · Severity: medium · CVSS 4.3 · Published 2026-10-26

iFlytek astron-agent is an agentic workflow platform that manages files and knowledge across users. An authenticated user can bypass ownership checks to read knowledge records from files owned by other users by adding a numeric space-id header to requests, gaining unauthorized access to sensitive information.

Technologies: iFlytek Astron-Agent. Vendors: iFlytek.

Quick answers

Is CVE-2026-116340 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-116340 being exploited in the wild.
How severe is CVE-2026-116340?
Medium severity, with a CVSS score of 4.3, published 26 October 2026.
Which products and versions are affected?
iFlytek Astron-Agent up to 1.1.2.
Is there a fix for CVE-2026-116340?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-116340 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-116340?
Check whether you run iFlytek Astron-Agent at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The FileInfoV2Service.listKnowledgeByPage endpoint skips object-level authorization checks when a client-supplied space-id header is parseable by Long.parseLong(), even if the value differs from the authenticated user's actual space ID. An attacker with a valid Console session JWT can exploit this to read knowledge records from arbitrary files via a simple header manipulation, though the vulnerability is read-only and requires prior knowledge of victim file IDs.

Affected products

  • iFlytek astron-agent up to 1.1.2

Timeline

  • 2026-10-26: disclosed
  • exploited: publicly available proof-of-concept code

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.