CVE-2026-17529 AstrBotDevs CVE debrief

Who should care

Users of AstrBotDevs AstrBot up to 4.25.5, operators, platform administrators, vulnerability management teams, and security teams should be aware of this vulnerability and take necessary actions to mitigate the risk.

Technical summary

The vulnerability is caused by incorrect authorization in the astrbot/core/astr_main_agent.py file of AstrBotDevs AstrBot up to 4.25.5. The manipulation of the argument req.func_tool leads to incorrect authorization. The attack may be initiated remotely, and the exploit is publicly available. Users should review and update AstrBotDevs AstrBot to version 4.25.6 or later. It is recommended to apply the patch with identifier d23011262e8e75e1ec41b0f1f0091493a022327e. Additionally, users should monitor for suspicious activity in the astrbot/core/astr_main_agent.py file and verify the affected scope to take necessary actions to mitigate the risk.

Defensive priority

Low

Recommended defensive actions

• Apply the patch with identifier d23011262e8e75e1ec41b0f1f0091493a022327e.
• Review and update AstrBotDevs AstrBot to version 4.25.6 or later.
• Monitor for suspicious activity in the astrbot/core/astr_main_agent.py file.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record was published on 2026-07-27T16:17:04.310Z and was last modified on 2026-07-27T20:25:13.817Z. The NVD entry is currently Deferred. The vulnerability affects AstrBotDevs AstrBot up to 4.25.5, specifically in the astrbot/core/astr_main_agent.py file. The manipulation of the argument req.func_tool leads to incorrect authorization. The attack may be initiated remotely. The exploit is publicly available. Users should verify the affected scope and take necessary actions to mitigate the risk.

Official resources