# CVE-2026-108548: AstronRPA through 1.1.6 Authentication Bypass via Arbitrary Bearer Token

> Unauthenticated attackers can bypass authentication in AstronRPA by sending arbitrary Bearer tokens to access protected APIs and impersonate users.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-fh8f-pxvw-9f29

## What is CVE-2026-108548?

CVE-2026-108548 is a medium-severity authentication bypass vulnerability in iflytek astron-rpa, published on 10 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AstronRPA through 1.1.6 contains an authentication bypass vulnerability in the OpenResty gateway's auth_handler.lua that accepts any Bearer token without validation. Unauthenticated attackers can send arbitrary Bearer values to reach /api/resource/ and /api/rpa-ai-service/ routes and spoof X-User-Id or user_id headers to act as any user.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-108548?


## How do I fix CVE-2026-108548?

No fix has been published for CVE-2026-108548 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-108548 being exploited?

There is no known exploitation of CVE-2026-108548 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-108548 and fix it if it is affected.

What it is: CVE-2026-108548 is a medium-severity authentication bypass vulnerability in iflytek astron-rpa, published on 10 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108548 in the wild and no public exploit code.

Affected product: iflytek astron-rpa. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-108548/ (Markdown: https://insights.sbomify.com/CVE-2026-108548/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-108548
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-108548
- OSV: https://osv.dev/vulnerability/CVE-2026-108548

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-108548/
Summaries are generated and may contain mistakes; the official description above is the record.