Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain on-path network position between client and server
-
DeliveryServe malicious update manifest over plain HTTP
-
Exploitelectron-updater fetches unsigned NSIS installer
-
ExecutionInstaller runs with no signature verification
-
ImpactExecute arbitrary code as desktop user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V15 - Secure Coding and Architecture Code integrity verification
|
| Exploitation Conditions | Requires the attacker to hold an on-path / man-in-the-middle position between the AstronRPA desktop client and its update server, because the auto-update feed is retrieved over plaintext HTTP with no transport encryption, and electron-updater is configured (per the public electron-builder.json) to install the NSIS installer without signature verification. Exploitation also depends on the client performing an update check that the attacker can intercept (the UI:P / passive user-interaction factor). Limiting factors: the MITM prerequisite (local network, rogue AP, compromised gateway, or on-path upstream) is non-trivial and corresponds to the vendor's AC:H and AT:P ratings, so this is not a scalable remote drive-by; it is confined to the AstronRPA desktop client at versions through 1.1.6 on networks the attacker can position within. |
| Impact | Signals point to a genuine but conditional threat rather than a mass-exploitation emergency. The vendor-assigned CVSS 4.0 vector (AV:N/AC:H/AT:P/PR:N/UI:P, score 7.7 High) is internally consistent with the description: unauthenticated (PR:N) network attacker, but with meaningful friction - high attack complexity (AC:H), a present attack requirement (AT:P, i.e. the attacker must be on-path at update time), and passive user interaction (UI:P) to trigger the auto-update check. Impact is full code execution as the desktop user (VC:H/VI:H/VA:H), confirming high technical impact. No EPSS score, no CISA KEV listing, and no public POC were provided, so exploitation probability signals are entirely absent rather than low - do NOT read the missing EPSS as evidence of low risk. SSVC inputs were not provided. The practical gating factor is the man-in-the-middle precondition plus plaintext-HTTP update feed; this is not automatable at internet scale and favors targeted or local-network adversaries (rogue Wi-Fi, compromised router, on-path ISP/enterprise segment) over worm-like spread. Net: treat as a real supply-chain/update-integrity priority for environments running the AstronRPA desktop client on untrusted networks, but it is not a remotely-wormable drive-by. |
| Exploit ScenarioDerived | An attacker on the same network as a victim (e.g., a malicious Wi-Fi hotspot or compromised router) intercepts the AstronRPA desktop client's plaintext-HTTP update check and returns a crafted update manifest pointing to a malicious NSIS installer. Because electron-updater is configured without signature verification, the client downloads and runs the attacker's installer, executing arbitrary code in the user's context. No public exploit was identified at time of analysis, but the flaw is a well-understood electron-updater misconfiguration class and the vulnerable config is visible in the project's public electron-builder.json. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
Remote code execution on the AstronRPA desktop client through version 1.1.6 is achievable by an on-path attacker who intercepts the client's plaintext HTTP auto-update check and serves a malicious update manifest with an unsigned NSIS installer, which electron-updater installs without verifying a publisher signature. The weakness is CWE-494 (download of code without integrity check), rated 7.7 under CVSS 4.0 with High attack complexity and attack requirements Present because the attacker must already hold a man-in-the-middle position and the client must run an update check; there is no public exploit identified at time of analysis and no vendor-released patch identified at time of analysis, so this is a conditional, non-scalable threat rather than a mass-exploitation emergency.
RemediationAI
No vendor-released patch has been identified at time of analysis, so remediation must begin with configuration hardening on the client build and network controls around it. The most direct fix is to enable update signature verification in the Electron build configuration, setting a trusted publisher name (publisherName / verifyUpdateCodeSignature) so electron-updater rejects the unsigned NSIS package, and to move the update feed to HTTPS with certificate validation and pinning so a manifest cannot be substituted in transit; publishing signed Installers and manifests closes both halves of the flaw. While a fixed build is unavailable, operators should disable the auto-update mechanism and perform manual, out-of-band upgrades from a trusted source, accepting the trade-off that clients stop receiving automatic fixes and must be patched by hand; alternatively, restrict endpoint network egress to only the legitimate update host and block plaintext HTTP update retrieval at the proxy or firewall, which prevents interception but requires accurate allow-listing and may break other HTTP-dependent client features. On managed fleets, avoid running the client on untrusted or shared networks or force traffic through a trusted VPN, and monitor DNS and HTTP requests for unexpected update manifest retrieval or installer downloads as a detection measure. Track the upstream fix via GitHub issue 894 and the VulnCheck advisory for a patched release before re-enabling automatic updates.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
AstronRPA ships an Electron desktop client whose self-update path is handled by electron-updater and configured through frontend/packages/electron-app/electron-builder.json (referenced directly in the advisory). Two design decisions combine into the flaw: the update feed is retrieved over plaintext HTTP, so the channel is neither encrypted nor authenticated, and the build configuration does not enforce Windows code-signing validation of the downloaded package (no publisher-name or verifyUpdateCodeSignature enforcement), so the NSIS installer produced for that feed is accepted without an integrity or authenticity check. An attacker positioned between client and update server therefore answers the update request with a crafted manifest pointing at an attacker-controlled installer, and the updater executes it in the context of the logged-on desktop user. The CWE-494 root cause is precisely this missing verification step; the CVSS 4.0 vector AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N reflects an unauthenticated network attack that nevertheless requires the attacker to be on path (AT:P), is non-trivial to arrange (AC:H), needs the client to perform an update check (UI:P), and yields high confidentiality, integrity and availability impact confined to the vulnerable system. This is consistent with the independent assessment of CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H. Note that the public tags on this record label it Information Disclosure, which understates the code-execution impact described by the advisory and reflected in both vectors.
Know when Electron gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
MITM position and timed update interception justify AC:H; no credentials needed so PR:N; the client must initiate/accept an update giving UI:R; malicious install yields full C:H/I:H/A:H.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
AstronRPA through 1.1.6 contains a download of code without integrity check vulnerability that allows network attackers to deliver malicious updates by abusing the desktop client's auto-update mechanism. Attackers positioned between the client and server can serve a malicious update manifest and NSIS installer, which electron-updater installs without signature verification, executing code as the desktop user.
Executive ViewAI
AstronRPA desktop clients through version 1.1.6 are vulnerable to remote code execution when an attacker intercepts the update process, potentially compromising endpoints and exposing sensitive data. With no vendor-released patch identified at time of analysis and no public exploit identified at time of analysis, leadership should prioritize interim mitigations to protect affected users and prevent lateral movement.
Disable automatic updates, block plaintext HTTP update traffic, enforce network segmentation, and monitor for suspicious update activity.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
GitHub Electron versions 1.8.2-beta.3 and earlier, 1.7.10 and earlier, 1.6.15 and earlier has a vulnerability in the pro
Remote code execution in 5ire 0.15.2 and earlier arises because the desktop AI assistant renders Mermaid diagrams with s
Cross-site scripting in DeepChat's Mermaid diagram renderer escalates to full remote code execution on affected desktop
Remote code execution in DeepChat 0.5.1 and below is possible through a cross-site scripting flaw in Mermaid diagram ren
Stored cross-site scripting in SiYuan through 3.8.4 lets an attacker who can set a notebook name containing an HTML payl
GitHub Electron before 1.6.8 allows remote command execution because of a nodeIntegration bypass vulnerability. Rated hi
GitHub Electron 1.7.15, 1.8.7, 2.0.7, and 3.0.0-beta.6, in certain scenarios involving IFRAME elements and "nativeWindow
Electron version 1.7 up to 1.7.12; 1.8 up to 1.8.3 and 2.0.0 up to 2.0.0-beta.3 contains an improper handling of values
electron-updater allows for automatic updates for Electron apps. Rated high severity (CVSS 7.5), this vulnerability is r
Cross-origin read bypass in Electron's custom protocol handler exposes sensitive application data to remote pages via fe
Native code execution outside the Chromium sandbox is achievable in Electron prior to 39.8.9, 40.9.2, 41.2.1, and 42.0.0
In Electron before versions 7.2.4, 8.2.4, and 9.0.0-beta21, there is a context isolation bypass. Rated critical severity
EUVD-2026-95908
GHSA-mj3v-h93p-hj6p
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB