# CVE-2026-108548: AstronRPA authentication bypass in OpenResty gateway

Source: https://junglewise.ai/threats/cve-2026-108548-astronrpa-through-1-1-6-contains-an-authentication-bypass  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-10. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-108548 · Severity: high · CVSS 7.3 · Published 2026-10-10

AstronRPA is an automation platform that orchestrates repetitive business processes. The gateway that sits in front of its APIs contains a critical authentication flaw: it accepts any Bearer token without validation, allowing unauthenticated attackers to reach protected API endpoints and impersonate any user. This could lead to unauthorized access to automation jobs, sensitive data, or malicious process execution.

Technologies: [iFlytek AstronRPA](https://junglewise.ai/threats/technologies/astronrpa). Vendors: [iFlytek](https://junglewise.ai/threats/vendors/iflytek).

## Quick answers

**Is CVE-2026-108548 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-108548 being exploited in the wild.

**How severe is CVE-2026-108548?** High severity, with a CVSS score of 7.3, published 10 October 2026.

**Which products and versions are affected?** iFlytek AstronRPA through 1.1.6.

**Is there a fix for CVE-2026-108548?** 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-108548 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-108548?** Check whether you run iFlytek AstronRPA 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 OpenResty gateway's auth_handler.lua does not validate Bearer tokens before accepting them, and the backend API dependencies accept arbitrary X-User-Id or user_id header values without verifying the authenticated user. An unauthenticated attacker can send any Bearer token to bypass authentication and set custom user ID headers to spoof identity, gaining access to /api/resource/ and /api/rpa-ai-service/ routes. This is a complete authentication bypass requiring only network access.

## Affected products

- iflytek AstronRPA through 1.1.6

## Timeline

- 2026-10-10: disclosed

## References

- [https://github.com/iflytek/astron-rpa](https://github.com/iflytek/astron-rpa)
- [https://github.com/iflytek/astron-rpa/blob/v1.1.6/backend/ai-service/app/dependencies/__init__.py](https://github.com/iflytek/astron-rpa/blob/v1.1.6/backend/ai-service/app/dependencies/__init__.py)

## Related threats

- [AstronRPA missing tenant authorization check in robot-service](https://junglewise.ai/threats/cve-2026-108547-astronrpa-through-1-1-6-contains-a-missing-tenant-authorization)
- [AstronRPA code integrity check bypass in auto-update](https://junglewise.ai/threats/cve-2026-108160-astronrpa-through-1-1-6-contains-a-download-of-code-without)
- [AstronRPA cross-site scripting in smart-component chat](https://junglewise.ai/threats/cve-2026-108159-astronrpa-through-1-1-6-contains-a-cross-site-scripting)
