Security Resilience

CVE-2026-90817

RCE in Vanderbilt Redcap 13.3.0 – 16.0.49

CISA KEVActive ExploitationEUVD ExploitedRCEPath Traversal
Published
20 September 2026
Modified
19 November 2026
KEV Added
18 November 2026
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.26 98th percentile
Risk Priority 97 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-90817 is a critical-severity External Control of File Name or Path (CWE-73) vulnerability in Vanderbilt Redcap. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Office Test (T1137.002); ranked in the top 2% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

Advisories

EU & UK References

Vulnerability Data

An unauthenticated Remote Code Execution vulnerability was found in the survey passthrough routing and Data Import processing logic, in which a malicious user could potentially exploit it by manipulating HTTP requests to access an unintended controller route from a public…

more

survey context and by supplying a crafted file-path/stream parameter during import handling. If successfully exploited, this could allow the attacker to remotely execute arbitrary code on the REDCap server. The attacker does not have to be authenticated in order to exploit this, but exploitation requires knowledge of a valid public survey hash. This vulnerability exists in REDCap 13.3.0 and higher.

CWE(s)
KEV Date Added
18 November 2026

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1137.002 Office Test Persistence
Adversaries may abuse the Microsoft Office "Office Test" Registry key to obtain persistence on a compromised system.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1216.001 PubPrn Stealth
Adversaries may use PubPrn to proxy execution of malicious remote files.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2019-10758Shared CWE-94both on KEV
CVE-2018-7602Shared CWE-94both on KEV
CVE-2013-3906Shared CWE-94both on KEV
CVE-2021-22205Shared CWE-94both on KEV
CVE-2025-4428Shared CWE-94both on KEV
CVE-2026-65660Shared CWE-94both on KEV
CVE-2022-3236Shared CWE-94both on KEV
CVE-2026-15410Shared CWE-94both on KEV
CVE-2017-9822Shared CWE-94both on KEV
CVE-2014-4148Shared CWE-94both on KEV

Affected Assets

vanderbilt
redcap
13.3.0 — 16.0.49 · 16.1.0 — 17.3.10 · 17.4.0 — 17.4.4

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2
  • V1.3.1

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Enforces authorization checks on the actual resource accessed, blocking unauthorized files even when a malicious path is supplied.

Least privilege limits the damage an injected code fragment can perform once executed.

Developer testing and evaluation finds code paths that accept and execute externally influenced strings.

Requiring documented secure development standards and tools enforces use of safe code-generation APIs and escaping.

Input validation directly rejects or sanitizes untrusted path strings before they reach filesystem operations.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 full match
blocks

Secure SDLC practices include input validation and path sanitization that eliminate this weakness.

PR.AA-05 mostly match
blocks

Least-privilege file authorization directly limits damage from externally controlled paths.

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

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

A.8.29's programme of code review, static analysis, dynamic testing and penetration testing is the complete pre-production discovery set for code injection: eval/dynamic-execution sinks are visible to SAST, code review catches them, and penetration testing reaches the externally exploitable instances, with no nameable remainder.

prevents

Training developers about input validation and path handling reduces instances of CWE-73 but is fallible human practice; the weakness is a code-level implementation defect that training alone cannot fully prevent, leaving a nameable remainder of cases where developers still write unvalidated path operations.

prevents

Secure coding standards require canonicalization, allow-listing, and bounds checks on file paths, directly eliminating CWE-73.

prevents

A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so a well-implemented clause reduces ordinary software weaknesses like CWE-73 in delivered code the way those practices do, at partial -- the same reading the owner applied to A.8.30 vs CWE-134.

finds

A.8.8's reach is DISCLOSURE-based: it finds CWE-73 where the weakness surfaces as a published advisory in a third-party component (CVE-2022-45918, CVE-2008-5748, CVE-2008-5764 are examples), but the bulk of CWE-73 instances live in first-party code where static analysis and code review — A.8.29's territory — are the High-rated detection methods, leaving the disclosed share a minority.

References