Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability

🚨SEVERITY: CRITICAL β€” CVSS 9.8Security Advisory

TL;DR πŸ“Œ

  • Vanderbilt University Research Electronic Data Capture (REDCap) contains a code injection vulnerability which could allow an unauthenticated attacker to execute arbitrary code on the server. An attacker could exploit this via crafted HTTP requests that access an unintended controller route from a public survey context and supply a crafted file-path or stream parameter during data…
  • Highest CVSS: 9.8 (Critical).
  • Listed in CISA KEV (2026-11-18) β€” this is being exploited in the wild.
  • Check the advisory for fixed releases β€” remediation detail is in the vendor link below.
  • CVEs: CVE-2026-90817.

What it is

CVE-2026-90817 is a code injection vulnerability in REDCap, the clinical data capture platform developed by Vanderbilt University. The flaw sits in the survey passthrough routing and Data Import processing logic.

An attacker reaches it by manipulating HTTP requests to access an unintended controller route from a public survey context, then supplying a crafted file-path or stream parameter during import handling. This does not require authentication to the REDCap application itself, but it does require knowledge of a valid public survey hash β€” the identifier used in public survey links. Given that hash, the attacker can route requests into the import processing code path that was not meant to be reachable from the public survey side.

Successful exploitation results in arbitrary code execution on the REDCap server. The vector (AV:N/AC:L/PR:N/UI:N) confirms this is remote, low-complexity, requires no privileges and no user interaction beyond the attacker’s own requests, and the impact rating (C:H/I:H/A:H) reflects full compromise of confidentiality, integrity and availability on that server.

This is listed in CISA’s Known Exploited Vulnerabilities catalogue, added 18 November 2026, so it is known to be exploited. The affected range is stated as REDCap 13.3.0 and higher.

What to do

  • Treat this as an active threat to any internet-facing REDCap instance, particularly those serving public surveys β€” public survey hashes are, by design, distributed outside your authentication boundary, so “we don’t publish the link” is not a control.
  • Check with Vanderbilt/the REDCap advisory for a fixed release; no fixed version is listed here, so confirm current patch status directly with the vendor rather than assuming a specific build is safe.
  • If REDCap is reachable from the internet and no patched build is available yet, consider restricting access to survey endpoints (e.g. via reverse proxy or WAF rules blocking requests to the import/data-processing controller routes from public survey paths) as an interim mitigation.
  • Review REDCap and web server logs for unexpected requests to import-processing routes originating from survey-hash URLs, especially those containing file-path or stream-like parameters.
  • Given the KEV listing, prioritise this over routine patch cycles and confirm remediation status to leadership as an exploited, unauthenticated RCE affecting internet-exposed research infrastructure.

For leadership 🧭

Executive summary. Any REDCap server exposed to the internet and serving public surveys can be fully taken over by someone who simply knows a survey link, with no login required. This is already listed as actively exploited, so it needs treating as an emergency rather than part of the normal patch cycle.

Why it matters:

  • The flaw lives in REDCap’s survey passthrough routing and Data Import processing, letting a crafted request reach import code that public survey visitors were never meant to touch.
  • Exploitation needs only a valid public survey hash β€” the identifier handed out in ordinary survey links β€” not a REDCap login, so anyone who has received or found a survey URL is a potential attack path.
  • Successful exploitation gives full remote code execution on the server, with confidentiality, integrity and availability all rated as completely compromised, putting research and clinical data at risk.
  • CISA added this to its Known Exploited Vulnerabilities catalogue on 18 November 2026, meaning this is not a theoretical weakness but one already being used against REDCap deployments.

Now / Next / Later:

  • Now: Identify every REDCap instance reachable from the internet, especially ones serving public surveys, and check each against Vanderbilt’s REDCap advisory for a fixed build before doing anything else.
  • Next: Where a fix isn’t yet confirmed available, add reverse proxy or WAF rules blocking requests into import/data-processing controller routes when they originate from public survey-hash paths, and review logs for requests to those routes carrying file-path or stream-style parameters.
  • Later: Once patched, build a standing process to track REDCap security advisories and KEV additions specifically, given that public survey hashes are inherently exposed outside your authentication boundary and similar routing issues could recur.

Source