Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local access with low privileges
-
DeliveryCraft malicious action argument
-
ExploitSubmit to evalAction in Remotedev Server
-
ExecutionTrigger code injection (CWE-94)
-
ImpactExecute attacker code in dev-tools process
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires local access to a system running the redux-devtools 5.0.0 Remotedev Server component (AV:L) together with low-level privileges (PR:L), after which a crafted value supplied to the action argument of the evalAction function results in code injection. No user interaction is required (UI:N). Exploitation is sharply limited by the local-only attack vector and the need for pre-existing privilege - this is developer/debugging infrastructure, so an attacker must already be able to reach the Remotedev Server locally. The precise trigger mechanism (how the action argument is reached and what input is accepted) is not described in the available sources, and no vendor-confirmed fix or affected-configuration guidance is available. |
| Impact | This is a low-priority issue despite its code-injection (CWE-94) classification, and the signals are internally consistent rather than conflicting. The reporter-supplied CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L) and resulting base score of 1.9 both point to a local, privilege-requiring flaw with only low impact to confidentiality, integrity and availability - not the network-exploitable RCE that the 'Code Injection'/'RCE' tags might suggest in isolation. There is no CISA KEV listing and no EPSS score provided, so there is no evidence of active or widespread exploitation; the vuln.today Decision label is 'monitor', the lowest urgency tier, which aligns with the low CVSS. The only exploitation signal is a public PoC reference (a GitHub issue), and per the input it is a reference only, not verified as working exploit code, so it should not be treated as a weaponized exploit. The disclosure note that the project 'has not responded yet' means no vendor-confirmed fix exists, but given local-only access and low impact this is a watch-and-patch-when-available item, not an emergency. The one caveat to verify: the 'RCE' tag overstates reach - the authoritative CVSS vector says the vector is local (AV:L), so confirm with the vendor/NVD before treating this as remotely exploitable. |
| Exploit ScenarioDerived | A user who already has local access to a machine running the Remotedev Server component passes a crafted value into the action argument handled by the evalAction function, causing attacker-controlled code to be injected and executed within the dev-tools server process. A public PoC reference exists as a GitHub issue, but it is not verified as working exploit code, so real-world exploitation would likely require an attacker to adapt it. Because the CVSS vector is AV:L/PR:L, the attacker needs local access and some existing privilege, which sharply limits realistic reach. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Code injection in the Remotedev Server component of redux-devtools 5.0.0 allows a locally positioned attacker with low-level privileges to inject code through a crafted value passed to the action argument of the evalAction function. Because the attack vector is local (AV:L) and requires pre-existing privileges (PR:L), the practical exposure is confined to developer and debugging environments where the Remotedev Server is reachable by an already-present user; no user interaction is needed. The flaw was reported to the project through a GitHub issue (reduxjs/redux-devtools#2125) but no vendor response or patch has been identified, and a public PoC reference exists that is not verified as working exploit code - no confirmed active exploitation (CISA KEV) was recorded, and the priority assessment is 'monitor'.
RemediationAI
No vendor-released patch has been identified at time of analysis: the problem was reported to the project early via issue https://github.com/reduxjs/redux-devtools/issues/2125 and has not yet received a vendor response, so no fixed version number can be cited. Until an upstream fix lands, the effective mitigation is to stop exposing the attack surface - do not run the Remotedev Server component of redux-devtools 5.0.0 on systems where untrusted or lower-privileged local users can reach it, and where remote debugging is genuinely required, prefer a separate disposable development host or container that holds no production credentials, at the cost of reduced debugging convenience. Running the tooling under an account with minimal privileges limits what injected code can reach but does not remove the injection itself, since the flaw already requires low privileges to trigger. Track the GitHub issue and the VulDB/NVD records (https://vuldb.com/vuln/427087, https://nvd.nist.gov/vuln/detail/CVE-2026-117526) for a patched release, and re-scan any environment pinned to redux-devtools 5.0.0 once a fix version is published.
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
The issue is a CWE-94 code injection flaw in redux-devtools, the widely used Redux debugging and state-inspection tooling, specifically in the Remotedev Server component that relays dispatched actions from an instrumented application to developer tooling. The evalAction function processes an attacker-influenced 'action' argument without adequate neutralisation, allowing crafted input to be interpreted as code rather than as inert data. CPE data identifies the affected package as cpe:2.3:a:reduxjs:redux-devtools with the EUVD record narrowing the affected release to version 5.0.0. The CVSS:4.0 vector supplied by the reporter is local-only (AV:L), low attack complexity (AC:L), requires low privileges (PR:L), and requires no user interaction (UI:N), with limited confidentiality, integrity and availability impact and no subsequent-system impact (SC:N/SI:N/SA:N). Our independent assessment concurs with CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L at a base score of 1.9 - the low severity is driven by the local attack path and the privilege prerequisite, not by any doubt about the injection mechanism. The precise trigger path (how the action argument is reached and which input is accepted) is not described in the available sources, so the exact preconditions beyond local access plus low privilege remain unverified.
Know when Redux Devtools 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:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Description states local access only (AV:L) and the vector requires existing low privilege (PR:L); code injection yields limited but real impact across C/I/A, so each is Low.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A vulnerability was found in reduxjs redux-devtools 5.0.0. Affected by this vulnerability is the function evalAction of the component Remotedev Server. The manipulation of the argument action results in code injection. The attack is only possible with local access. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.
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
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
EUVD-2026-111278
GHSA-5cc2-grjh-g3jv
NVD
CVE.org
EPSS
VulDB
Exploit-DB