Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-90817 – Unauthenticated Remote Code Execution – REDCap 13.3.0 and later

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-90817 is a critical, unauthenticated remote code execution vulnerability in Vanderbilt University’s REDCap, a widely deployed clinical and research data management platform. The flaw stems from unsafe routing in the survey passthrough mechanism combined with insecure file-path/stream handling in the Data Import module, allowing an attacker to reach unintended server-side controllers from a public survey context. Given its network attack vector, lack of authentication requirement, and full compromise potential, it carries a CVSS v3.1 score of 9.8 (Critical).

Technical details

  • Root cause: REDCap’s survey passthrough routing (via the __passthru mechanism) can be manipulated to reach controller routes that were never intended to be reachable from a public, unauthenticated survey context, including the Data Import processing logic.
  • Trigger conditions: An attacker supplies crafted file-path/stream parameters through this passthrough path, causing the Data Import handler to process attacker-controlled input in an unsafe way.
  • Attack vector: Network-based and unauthenticated; the only prerequisite is knowledge of a valid public survey hash (the s= parameter used to reach a live, published survey).
  • Impact: Successful exploitation results in arbitrary code execution on the REDCap server, with full loss of confidentiality, integrity, and availability of the host and the sensitive research/clinical data it stores.

Affected software

  • REDCap versions 13.3.0 and higher, up to but not including the patched releases below.
  • Versions confirmed not vulnerable (patched): 16.0.49 LTS, 17.3.10 LTS, and 17.4.4 Standard Release (and later).

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Associated weaknesses: CWE-94 (Improper Control of Generation of Code / Code Injection) and CWE-73 (External Control of File Name or Path).

Mitigation and recommended actions

  • Immediate: Upgrade REDCap to 16.0.49 LTS, 17.3.10 LTS, 17.4.4 Standard Release, or a later version that includes the fix.
  • If immediate patching is not possible:
    • Restrict or disable public survey access where not strictly required for operations, reducing exposure of the passthrough entry point.
    • Place REDCap instances behind a web application firewall capable of inspecting and blocking anomalous passthrough/routing parameters and Data Import requests originating from unauthenticated survey sessions.
    • Monitor REDCap access and application logs for unexpected requests to Data Import or passthrough routes originating from public survey URLs, and for unusual file-path or stream parameters in incoming requests.
    • Limit network exposure of REDCap servers to only the necessary user populations, and ensure the server is not otherwise reachable from the open internet beyond intended survey endpoints.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge