Cyber Resilience

CVE-2025-47774

Published
15 May 2025
Modified
17 June 2026
CVSS Score v4 2.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0042 35th percentile
Risk Priority 34 floored blend · peak EPSS

Summary

CVE-2025-47774 is a low-severity Insufficient Control Flow Management (CWE-691) vulnerability. Its CVSS base score is 2.9 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Hijack Execution Flow (T1574); ranked at the 35th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-2 (Separation of System and User Functionality) and SC-3 (Security Function Isolation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Vyper is the Pythonic Programming Language for the Ethereum Virtual Machine. In versions up to and including 0.4.2rc1, the `slice()` builtin can elide side effects when the output length is 0, and the source bytestring is a builtin (`msg.data` or…

more

`<address>.code`). The reason is that for these source locations, the check that `length >= 1` is skipped. The result is that a 0-length bytestring constructed with slice can be passed to `make_byte_array_copier`, which elides evaluation of its source argument when the max length is 0. The impact is that side effects in the `start` argument may be elided when the `length` argument is 0, e.g. `slice(msg.data, self.do_side_effect(), 0)`. The fix in pull request 4645 disallows any invocation of `slice()` with length 0, including for the ad hoc locations discussed in this advisory. The fix is expected to be part of version 0.4.2.

CWE(s)
CWE-691

Related Threats

MITRE ATT&CK Enterprise Techniques

T1574 Hijack Execution Flow Stealth
Adversaries may execute their own malicious payloads by hijacking the way operating systems run programs.
attack.mitre.org →
T1055 Process Injection Stealth
Adversaries may inject code into processes in order to evade process-based defenses as well as possibly elevate privileges.
attack.mitre.org →
T1055.003 Thread Execution Hijacking Stealth
Adversaries may inject malicious code into hijacked processes in order to evade process-based defenses as well as possibly elevate privileges.
attack.mitre.org →
T1055.004 Asynchronous Procedure Call Stealth
Adversaries may inject malicious code into processes via the asynchronous procedure call (APC) queue in order to evade process-based defenses as well as possibly elevate privileges.
attack.mitre.org →
T1574.004 Dylib Hijacking Stealth
Adversaries may execute their own payloads by placing a malicious dynamic library (dylib) with an expected name in a path a victim application searches at runtime.
attack.mitre.org →
T1055.005 Thread Local Storage Stealth
Adversaries may inject malicious code into processes via thread local storage (TLS) callbacks in order to evade process-based defenses as well as possibly elevate privileges.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-5938Shared CWE-691
CVE-2024-29079Shared CWE-691
CVE-2023-20559Shared CWE-691
CVE-2024-37158Shared CWE-691
CVE-2025-35963Shared CWE-691
CVE-2023-5102Shared CWE-691
CVE-2025-24305Shared CWE-691
CVE-2025-20022Shared CWE-691
CVE-2025-22893Shared CWE-691
CVE-2024-33617Shared CWE-691

Affected Assets

—
Ethereum Virtual Machine. In
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SC-2 Separation of System and User Functionality partial match

Separating user and system functionality structurally limits unexpected control-flow transfers between domains.

SC-3 Security Function Isolation partial match

Isolating security functions prevents control-flow tampering that would otherwise bypass or alter security decisions.

SC-39 Process Isolation partial match

Process isolation keeps execution domains separate so one process cannot hijack another's control flow.

SI-16 Memory Protection partial match

Memory protection blocks unauthorized code execution that would modify control flow at runtime.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC activities such as static analysis, code review, and testing directly prevent control-flow weaknesses while also addressing many other coding defects.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect control-flow weaknesses but does not itself implement preventive controls.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates structured control-flow design and review that directly reduces unexpected flow manipulation.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles require explicit control-flow integrity mechanisms and error-handling paths.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid constructs that allow unintended control-flow changes such as missing breaks or unsafe jumps.

A.8.32 Change management partial match
prevents

Change management reduces introduction of control-flow defects through controlled updates but does not address the weakness directly.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Windows 10 (1 rule)
  • V-220726 Data Execution Prevention (DEP) must be configured to at least OptOut. prevents CWE-691
Windows 11 (1 rule)
  • V-253283 Data Execution Prevention (DEP) must be configured to at least OptOut. prevents CWE-691

References