Vanderbilt University REDCap · Exploitation confirmed

[Single source] CISA confirms exploitation of code injection in REDCap

· 1 min read

CISA listed CVE-2026-90817 in its KEV catalog, confirming exploitation of the flaw. The code injection in Vanderbilt University's REDCap allows unauthenticated arbitrary code execution via crafted HTTP requests that reach an unintended route, requiring knowledge of a valid public survey hash. Exposed instances must apply vendor-recommended mitigations by the federal deadline of 2026-11-21.

Illustration: CISA confirms exploitation of code injection in REDCap
WhatsApp LinkedIn X
HighVulnerabilityExploitation confirmedFix unconfirmed

In 30 seconds

Observed

CISA has added CVE-2026-90817 to its Known Exploited Vulnerabilities catalog, the list the agency reserves for flaws it considers actively exploited. The bug is a code injection in REDCap, Vanderbilt University's Research Electronic Data Capture platform, and it can let an attacker run arbitrary code on the server without any login. Federal stakeholders now have a hard deadline of November 21, 2026 to apply vendor recommended mitigations.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

Observed

The attack, as described in the catalog entry, works through crafted HTTP requests that reach an unintended controller route from a public survey context during data import, and it only works if the attacker already knows a valid public survey hash. CISA lists ransomware use of this flaw as unknown.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

What happened

Observed

The decisive update landed on November 18, 2026, when the KEV entry for CVE-2026-90817 appeared in CISA's catalog. The entry identifies the affected product as Vanderbilt University's REDCap and classifies the issue as a code injection vulnerability that allows unauthenticated arbitrary code execution on the server.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

Observed

According to the technical description, an attacker sends crafted HTTP requests that access an unintended controller route from a public survey context and supplies a crafted file path or stream parameter while the system processes a data import. There is one important gate: exploitation requires knowledge of a valid public survey hash, the kind of identifier used to share public surveys.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

Observed

The listing comes with binding instructions. Stakeholders must apply mitigations in accordance with vendor instructions, comply with CISA's BOD 26-04 directive on prioritizing security updates based on risk and with the agency's Forensics Triage Requirements, follow the applicable BOD 26-04 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. The federal deadline is November 21, 2026, and each stakeholder is responsible for evaluating the internet exposure of their own assets.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

Why it matters

Inferred

REDCap exists to capture research data, so a server running it plausibly holds survey responses and study records that could be exposed or manipulated if someone gains code execution. That consequence is not spelled out in the catalog entry, but it follows directly from what the product is and what this flaw allows.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

Observed

For federal agencies and other BOD 26-04 stakeholders, the listing converts a theoretical risk into an operational mandate: mitigate by November 21, 2026, follow the directive's cloud guidance where relevant, or stop using the product if no mitigation exists. The entry also states plainly that stakeholders are responsible for judging which of their assets are exposed to the internet.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

Inferred

For operators outside the federal perimeter, the most reasonable reading is that CISA believes this bug has crossed from paper to practice, so any REDCap instance reachable from the internet deserves immediate attention rather than a wait and see approach.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

What to do

Observed

Apply the vendor recommended mitigations now rather than close to the deadline, and make sure the work satisfies BOD 26-04 prioritization guidance and CISA's Forensics Triage Requirements.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

Observed

If you run REDCap as a cloud service, follow the applicable BOD 26-04 cloud guidance. If no mitigation is available for your deployment, the entry's stated alternative is to discontinue use of the product. Also take stock of which instances are reachable from the internet, since the entry makes that evaluation each stakeholder's own responsibility.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

Confirmed and still uncertain

Observed

What is established: the vulnerability exists in REDCap, it allows unauthenticated arbitrary code execution through the described route, exploitation requires a valid public survey hash, CISA has listed it in KEV, and the federal deadline is November 21, 2026.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

Observed

What remains open: the entry lists ransomware use as unknown, and it says nothing about who is exploiting the flaw, when exploitation started, how many instances are exposed, or whether any specific organization has been compromised. Those questions need evidence beyond this catalog entry.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

What people are saying

Observed

The current evidence batch contains a single voice, CISA's catalog entry, which speaks through required actions and deadlines rather than quotations. No statement from Vanderbilt University, no researcher commentary, and no attacker claims appear in the material provided so far.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

Evolution

Observed

The one documented milestone so far is the KEV listing itself, dated November 18, 2026, with a federal remediation deadline of November 21, 2026, three days later. That is the entire recorded timeline in this batch.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

Inferred

Everything before the listing is missing here: how the flaw was found, when Vanderbilt was notified, whether a patch shipped before the catalog entry, and when CISA first observed exploitation. Reconstructing that chain will require vendor advisories or forensic reporting that the current evidence does not include.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

Reach

Observed

1 independent groups, 1 updates, and 0 engagements.

Technical detail

Observed

CVE-2026-90817 is a code injection vulnerability in Vanderbilt University's REDCap. An unauthenticated attacker can execute arbitrary code on the server by sending crafted HTTP requests that reach an unintended controller route from a public survey context, supplying a crafted file path or stream parameter during data import processing. The precondition is knowledge of a valid public survey hash.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

Observed

The entry anchors the flaw at NVD under CVE-2026-90817 and ties the response to CISA's BOD 26-04 directive and its Forensics Triage Requirements, the standard playbook references for KEV remediation.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

Sources and evidence

Observed

This story currently rests on one primary source: CISA's KEV catalog entry for CVE-2026-90817, dated November 18, 2026 and anchored at NVD. Every claim in this briefing traces back to that single item.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

Inferred

That is a thin base for a story about active exploitation. Independent confirmation of real world attacks, vendor advisory details, patch information, and forensic reporting are all absent from the batch, so the exploitation picture should be treated as what the catalog states, no more, until further evidence arrives.CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kevOpen original sourceSee in source list

Sources

  1. CVE-2026-90817: Vanderbilt University Research Electronic Data Capture (REDCap) (Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability)nvd.nist.gov · kev

Incidents like this, every morning

The ones that need action first, in a 3-minute read.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Get the next one tomorrow morning

One email a day with what changed, what to fix first and how.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Share it with your team

Whoever handles security with you should get it too.

LinkedIn X

Your colleague gets a confirmation request. Nothing is sent unless they confirm.

See all news

Read also

Before you go: get this every day

The HIFY Radar daily edition lands every morning with the incidents that need action. Free.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click