Skip to content
Breach Index · running record

Vanderbilt University Medical Center and REDCap vulnerabilities in 2026: CVE-2026-90817 (not a breach of Vanderbilt)

REDCap, the research data capture platform developed at Vanderbilt and licensed to thousands of universities, hospitals and research institutions, runs on each institution's own servers. This page tracks exploited REDCap vulnerabilities and attacks on REDCap servers; none is a breach of Vanderbilt.

Short answer

Was REDCap hacked?

No breach of Vanderbilt University Medical Center is reported: CVE-2026-90817 is a vulnerability in REDCap software that each institution hosts itself. Per the CVE record (CNA Securifera, 20 September 2026), an unauthenticated attacker who knows a valid public survey hash can run code on a REDCap server; it affects 13.3.0 and later, and the record lists 16.0.49, 17.3.10 and 17.4.4 as not affected.

CISA added it to KEV on 18 November 2026, due 21 November. Safe Security's 23 October roundup describes exploitation that installed a web shell and the XMRig cryptominer. Separately, GTIG reported in June 2026 that a China-nexus group, UNC6508, targets REDCap servers; GTIG did not tie that to this CVE.

Timeline at a glance

  1. 15 Jun 2026GTIG reports UNC6508 targeting REDCap servers at medical research institutions; initial access not confirmed. (GTIG)Reported
  2. 20 Sep 2026CVE-2026-90817 published: unauthenticated RCE in REDCap 13.3.0 and later. (CVE record (Securifera))Not a breach
  3. 23 Oct 2026Safe Security describes exploitation leading to a web shell and the XMRig miner. (Safe Security)Reported
  4. 18 Nov 2026CISA adds CVE-2026-90817 to KEV, due 21 November 2026. (CISA)Not a breach

Last updated 20 November 2026. Every entry is dated and linked to its source; claims by attackers are labelled as claims, never stated as fact.

Vanderbilt University Medical Center (REDCap) incident timeline, in detail

Confirmed = acknowledged by Vanderbilt University Medical Center (REDCap), a regulator filing or a court. Reported = credible reporting Vanderbilt University Medical Center (REDCap) has not fully confirmed. Unverified claim = an attacker or leak-site claim.

Sep-Nov 2026Not a breachProduct vulnerability (pre-authentication), known exploited

CVE-2026-90817: unauthenticated code execution through public surveys, exploited for cryptomining

What happened. Crafted requests reach an unintended controller route from a public survey and abuse data import handling with a crafted file path or stream, giving code execution on the server (CWE-73, CWE-94; CVSS 3.1 9.8). Needs a valid public survey hash. Affects 13.3.0 and later; 16.0.49 LTS, 17.3.10 LTS and 17.4.4 Standard are listed as not affected. Credit: Ryan Wincey (Securifera).

Impact. Safe Security says observed exploitation staged a temporary web shell, then XMRig disguised as image files and the syslog-ng process, with persistence through scheduled tasks and an added SSH key, and that patching does not remove payloads already deployed. CISA lists it as exploited (forensic triage "Yes").

Sources: CVE record · Safe Security · CISA KEV

Jun 2026ReportedEspionage campaign against REDCap hosts

UNC6508 targets REDCap servers at medical research institutions (GTIG)

What happened. GTIG says a China-nexus group it tracks as UNC6508 targeted externally facing REDCap servers and probed for vulnerable legacy versions. GTIG says it could not confirm how the group first got in.

Impact. GTIG says the group harvested REDCap login credentials and database and service-account credentials. It names no CVE and does not link this to CVE-2026-90817.

Sources: GTIG

Where the reports disagree

  • Who observed the cryptomining: Safe Security's roundup describes the exploitation without saying who observed it; The Hacker News and Security Affairs attribute it to Safe Security; a University of Florida scanner project credits a Palo Alto Networks Unit 42 report we could not find.
  • Fixed versions: REDCap's release notes are behind a community login. The versions here are the "unaffected" versions in the CVE record published by Securifera.

The pattern across the record

Research IT is often outside central IT

REDCap servers are usually run by research groups or clinical research offices, which makes them easy to miss in patch programmes.

Vulnerabilities are not breaches

Each institution hosts its own REDCap. A compromised server is that institution's incident, not Vanderbilt's.

What it means for Vanderbilt University Medical Center (REDCap) customers — and what to do

If your institution runs REDCap, the question is your version, whether public surveys are enabled and whether the server shows signs of compromise.

  1. 1.Upgrade REDCap

    16.0.49 LTS, 17.3.10 LTS or 17.4.4 Standard or later. Until then restrict or disable public surveys.

    What to do
  2. 2.Check for compromise

    Look for unexpected PHP files, a process posing as a system service using high CPU, new cron entries and unfamiliar SSH keys.

  3. 3.Bring in governance

    A server holding study data that was compromised is an incident for your IRB and privacy office, not only IT.

    IR Playbook Lab
Take this with you
Incident timeline · What Vanderbilt University Medical Center (REDCap) customers should do · Sources

CISO takeaways

Sources

Company statements and regulator filings first, then reputable reporting. Reviewed 20 November 2026.

  1. 1.CVE-2026-90817 (CNA Securifera) — CVE.org, 20 Sep 2026
  2. 2.This Week in CVEs: The Week Defenders Lost the Head Start — Safe Security, 23 Oct 2026
  3. 3.CISA Adds Four Known Exploited Vulnerabilities to Catalog — CISA, 18 Nov 2026
  4. 4.China-nexus actor targeting the medical research community — Google Threat Intelligence Group, 15 Jun 2026
  5. 5.REDCap community (release notes, login required) — Vanderbilt (REDCap), Nov 2026

Frequently asked questions

Was REDCap or Vanderbilt hacked?

No breach of Vanderbilt is reported. CVE-2026-90817 is a vulnerability in REDCap, which each institution hosts on its own servers; unpatched servers have been exploited.

Which REDCap versions fix CVE-2026-90817?

16.0.49 LTS, 17.3.10 LTS and 17.4.4 Standard or later, per the CVE record. Versions from 13.3.0 are affected.

Is CVE-2026-90817 exploited?

Yes. CISA added it to KEV on 18 November 2026 (due 21 November), and Safe Security describes exploitation that installed a cryptominer.

Same sourced, verification-tagged timeline, company by company — compare how peers have fared.

Or see the full Breach Index and how to read it.

Independent analysis for security-leadership education; not affiliated with or endorsed by Vanderbilt University Medical Center (REDCap). Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.