CVE-2026-108548

waiting for further signalsZero needs more public information before it can validate it.

GHSA-fh8f-pxvw-9f29 ↗EUVD-2026-96343 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
iflytek astron-rpa <= 1.1.6
ETK-2026-1177Zero's internal tracking ID, independent of the CVE number., permanent identifier
10d 11h 25msince last run
1h 13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h45m
0
+2h
+6h
+8h
+10h
+12h

description

AstronRPA through 1.1.6 has an authentication bypass in its OpenResty gateway. An unauthenticated attacker who can reach affected API endpoints may impersonate users by presenting an unvalidated bearer token and supplying identity-related request headers.

mitigation

Restrict access to the affected gateway API routes to trusted networks and enforce bearer-token validation at an upstream proxy or identity layer. Update when the vendor publishes a corrected release; the evidence does not identify a fixed version.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.29%20th percentile
agent run time
1h 13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-10 14:35Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-10 14:35Z
    ghsa: trigger signal, started the run
  2. 2026-10-10 14:35Z

this entry in the feed

GET /api/v1/feed/CVE-2026-108548

{
  "etk_id": "ETK-2026-1177",
  "cve_id": "CVE-2026-108548",
  "display_id": "CVE-2026-108548",
  "ghsa_id": "GHSA-fh8f-pxvw-9f29",
  "euvd_id": "EUVD-2026-96343",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Bearer-token authentication bypass in AstronRPA gateway",
  "summary": "AstronRPA through 1.1.6 has an authentication bypass in its OpenResty gateway. An unauthenticated attacker who can reach affected API endpoints may impersonate users by presenting an unvalidated bearer token and supplying identity-related request headers.",
  "mitigation": "Restrict access to the affected gateway API routes to trusted networks and enforce bearer-token validation at an upstream proxy or identity layer. Update when the vendor publishes a corrected release; the evidence does not identify a fixed version.",
  "vendor": "iflytek",
  "product": "astron-rpa",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.1.6"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "astron-rpa",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
  "epss_score": 0.0029,
  "epss_percentile": 0.2064,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 72.58716683333333,
  "t0_at": "2026-10-10T14:35:03.690000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-10T14:35:03.690000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-10T14:35:03.690000+00:00",
      "url": "https://github.com/advisories/GHSA-fh8f-pxvw-9f29"
    }
  }
}

published 2026-10-10 17:07Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.