CVE-2026-95929: iFlytek astron-agent advisory

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

What it is

A weakness has been identified in iFlytek astron-agent up to 1.0.7. Affected is an unknown function of the file console/backend/commons/src/main/resources/mapper/ChatBotMarketMapper.xml of the component getBotList API endpoint. Executing a manipulation of the argument sortDirection can lead to sql injection. It is possible to launch the attack remotely. Upgrading to version reward-1575 is able to address this issue. This patch is called 6702be70ae802b1048f5fbec91e690e7b71a4165. You should upgrade the affected component.

Description quoted from the CVE record (assigned by VulDB, published 2026-09-23).

Weakness: SQL Injection; Injection

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing low privileges and no user interaction. Impact: confidentiality low, integrity low, availability low. CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 3 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 6 references on Exploit Observer

Live scores

EPSS: 0.004
low predicted chance of attack
VEDAS: 0.986
strong exploit evidence
On CISA KEV: Not listed
Detection rule: Suricata

Who is affected

Product	Affected	Not affected
iFlytek astron-agent	version 1.0.0 version 1.0.1 version 1.0.2 version 1.0.3 version 1.0.4 version 1.0.5 version 1.0.6 version 1.0.7	reward-1575 is not affected

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

Vendor guidance:

https://github.com/iflytek/astron-agent/pull/1342 (issue-tracking, patch)
https://github.com/iflytek/astron-agent/commit/6702be70ae802b1048f5fbec91e690e7b71a4165 (patch)
https://github.com/iflytek/astron-agent/releases/tag/reward-1575 (patch)

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-95929 Astron-Agent - getBotList sortDirection SQL Injection Attempt. Add them to your Suricata rule set and reload.

Show the rules

suricata

alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-95929 Astron-Agent - getBotList sortDirection SQL Injection Attempt"; flow:established,to_server; http.method; content:"POST"; http.request_body; content:"sortDirection"; nocase; fast_pattern; pcre:"/\x22sortDirection\x22\s*:\s*\x22[^\x22]*(?:\x28|\x2c|select|sleep|benchmark|union|updatexml|extractvalue|case\s+when|if\x28|\x2d\x2d|\x23)/i"; classtype:web-application-attack; reference:cve,CVE-2026-95929; reference:url,https://www.exploit.observer/?keyword=CVE-2026-95929&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=astron-agent&match=exact; sid:1094800; rev:1;)

CVE-2026-95929.rules on GitHub

References

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.