TL;DR: Organizations running REDCap 13.3.0 or later must apply vendor-issued mitigations immediately in line with CISA BOD 26-04 guidance; if patches are unavailable, CISA directs discontinuing use of the product.
What Is the Vulnerability?
CVE-2026-90817 is an unauthenticated Remote Code Execution (RCE) vulnerability in Vanderbilt University Research Electronic Data Capture (REDCap), a widely used web application for building and managing research databases and surveys. It carries a CVSS 3.1 score of 9.8 (Critical) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, meaning it is network-reachable, requires no privileges, and demands no user interaction.
Two weaknesses underpin the vulnerability:
- CWE-73 — External Control of File Name or Path: An attacker can manipulate HTTP requests to supply a crafted file-path or stream parameter during Data Import processing, causing the application to interact with attacker-controlled paths.
- CWE-94 — Improper Control of Generation of Code (Code Injection): By accessing an unintended controller route through the survey passthrough routing mechanism, an attacker can inject and execute arbitrary code on the server.
According to the NVD description, the attack chain works as follows: the attacker crafts HTTP requests that (1) reach an unintended controller route via the public survey passthrough context, then (2) supply a malicious file-path or stream parameter during data import handling. Together, these two steps can result in arbitrary code execution on the REDCap server.
One notable precondition reduces the pool of opportunistic attackers somewhat: exploitation requires knowledge of a valid public survey hash. However, authentication itself is not required, and in environments where surveys are widely distributed, survey hashes may be easy to obtain or enumerate.
Who and What Is Affected?
The vulnerability exists in REDCap version 13.3.0 and all higher versions up to the patched release, as stated in the NVD advisory. Any organization that:
- Hosts a REDCap instance on version 13.3.0 or later,
- Has at least one publicly accessible survey (i.e., a survey with a public, shareable hash), and
- Has not applied the vendor's remediation guidance
…should consider their REDCap deployment at risk. REDCap is extensively deployed across academic medical centers, universities, hospitals, and research institutions globally. Because surveys are frequently shared with study participants outside organizational networks, the attack surface for the survey passthrough route is often intentionally public-facing.
Self-hosted and consortium-hosted REDCap installations are both in scope. Organizations should verify their deployed version immediately via their REDCap administration panel.
What Is the Potential Impact?
Successful exploitation of CVE-2026-90817 gives an unauthenticated attacker full remote code execution on the underlying REDCap server. The CVSS confidentiality, integrity, and availability scores are all rated High, reflecting the breadth of potential harm:
- Confidentiality: An attacker could access research databases, participant records, clinical data, and any other data stored on or accessible from the REDCap server — including data subject to HIPAA, FERPA, or other regulatory frameworks depending on the institution.
- Integrity: Arbitrary code execution allows an attacker to modify or corrupt research data, alter survey logic, insert malicious content, or tamper with study results.
- Availability: The attacker could crash services, delete data, or use the compromised server as a pivot point for further attacks within the institutional network.
CISA added this vulnerability to the Known Exploited Vulnerabilities (KEV) catalog on 2026-11-18, confirming that exploitation has occurred. CISA's KEV summary specifically notes the attack vector — crafted HTTP requests exploiting the survey passthrough route and data import processing — as the observed exploitation mechanism.
Given REDCap's role in storing sensitive research and in some cases protected health information, the downstream consequences of a successful compromise can extend well beyond the application itself.
What Should You Do Right Now?
CISA's required action for KEV entries covering this vulnerability directs organizations to:
- Apply mitigations in accordance with vendor instructions. Consult the official Vanderbilt University / REDCap vendor advisory for the specific patch or configuration change required. REDCap administrators should log in to the REDCap Community (community.project-redcap.org) for official guidance, as Vanderbilt distributes updates and security advisories through that channel.
- Comply with CISA BOD 26-04. CISA's Binding Operational Directive 26-04 establishes risk-prioritized patching timelines for federal agencies; non-federal organizations subject to this directive or choosing to follow it should ensure they meet the applicable deadlines. BOD 26-04 also includes specific guidance for cloud-hosted services.
- Follow CISA Forensics Triage Requirements. Because active exploitation has been confirmed, CISA directs affected stakeholders to conduct forensic triage per the referenced guidance. Assume any vulnerable, internet-exposed REDCap instance may already be compromised and investigate accordingly before patching.
- Discontinue use if mitigations are unavailable. If a patch or effective mitigation cannot be applied, CISA's guidance is to discontinue use of the product.
As interim risk-reduction steps (pending or in addition to patching), administrators should consider:
- Reviewing all active public surveys and disabling any that are not strictly necessary to reduce the number of valid, publicly known survey hashes.
- Restricting network access to the REDCap Data Import and survey passthrough endpoints at the firewall or web application firewall layer where operationally feasible.
- Reviewing server and application logs for anomalous HTTP requests targeting survey passthrough or data import routes, particularly requests with unexpected file-path parameters.
- Ensuring REDCap servers are segmented from broader institutional networks to limit lateral movement in the event of compromise.
How External Testing Surfaces This Exposure
Point-in-time external vulnerability assessments can help organizations understand whether their REDCap deployment is exposed before an attacker finds it. From the outside, a tester evaluating a REDCap instance would look at several indicators of exposure:
- Version fingerprinting: REDCap often reveals its version string in page source, HTTP headers, or administrative endpoints. Confirming a version of 13.3.0 or higher without evidence of patching immediately flags the host as potentially vulnerable.
- Survey endpoint enumeration: The presence of publicly accessible survey routes is a prerequisite for exploitation. An external scan can identify which survey-related endpoints are reachable without authentication, clarifying the actual attack surface.
- Web application scanning: Automated and manual web application testing can probe the data import and survey passthrough routes for the class of parameter manipulation described in this vulnerability (CWE-73/CWE-94), without executing any payload, to confirm whether protective controls such as input validation or WAF rules are in place.
- Network exposure review: Confirming whether the REDCap server is internet-facing or restricted to internal networks is fundamental context — internet-exposed instances face a materially higher risk given CISA's confirmation of active exploitation.
Because this CVE is in the CISA KEV catalog, any external assessment of an organization's attack surface should treat an unpatched, internet-facing REDCap instance as a priority finding requiring immediate escalation.
Sources & further reading: NVD CVE-2026-90817 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: securifera.com, cisa.gov. This advisory contains no exploit code.
Frequently asked questions
Does an attacker need an account on our REDCap system to exploit CVE-2026-90817?
No. Authentication is not required. The only precondition is knowledge of a valid public survey hash, which is a unique identifier attached to publicly accessible surveys. No login credentials are needed.
Which REDCap versions are affected?
According to the NVD advisory, the vulnerability exists in REDCap 13.3.0 and all higher versions. Organizations should check their installed version via the REDCap administration panel and consult the vendor's official advisory for the specific patched version.
Is this vulnerability being actively exploited?
Yes. CISA added CVE-2026-90817 to its Known Exploited Vulnerabilities (KEV) catalog on 2026-11-18, which indicates that exploitation has been observed. Organizations with internet-exposed REDCap instances running affected versions should treat this as an active threat and prioritize remediation accordingly.
If we cannot patch immediately, is there anything we can do to reduce risk?
Yes, though these steps supplement rather than replace patching. Consider disabling public surveys that are not operationally essential (reducing the number of valid, exploitable survey hashes), restricting network-level access to data import and survey passthrough endpoints where feasible, and reviewing logs for anomalous requests targeting those routes. CISA's guidance also states that if mitigations cannot be applied, discontinuing use of the product should be considered.