Security Digest · Nov 18, 2026 · Vulnerability · Other

REDCap CVE-2026-90817: Exploited Unauthenticated RCE

REDCap 13.3.0+ lets anyone with a public survey link run code on the server. In CISA KEV Nov 18. Fixed in 16.0.49, 17.3.10, 17.4.4. Patch now.

Our verdict

Act now

If you run REDCap 13.3.0 or later below 16.0.49, 17.3.10 or 17.4.4, upgrade today: the only precondition is a public survey link, the fix has existed since September, and CISA now lists the flaw as exploited.

Who must act: Universities, hospitals and research groups that host their own REDCap server, especially any that publish public surveys on the internet, including department- or lab-run instances outside central IT.

Who can relax: Researchers and survey participants who use an institution's REDCap without running the server, and instances already on 16.0.49, 17.3.10, 17.4.4 or later.

Affected
REDCap 13.3.0 and later without the September 9, 2026 fix
REDCap LTS 16.0.x before 16.0.49
REDCap LTS 17.3.x before 17.3.10
REDCap Standard 17.4.x before 17.4.4
Other release lines from 13.3.0 on, such as 16.1.x and 17.0 to 17.2 (no fixed build listed; move to a fixed line)
Fixed in
REDCap 17.4.4 (Standard)
REDCap 17.3.10 (LTS)
REDCap 16.0.49 (LTS)
CVSS
9.8 (v3.1, CNA)
EPSS
33.4% (percentile 98)
CISA KEV
Yes, listed as known exploited
Exploitation
Exploited in the wild
Severity
Critical

What to do

  1. Inventory every REDCap server you run, including department and lab instances, and check each version on the Control Center home page.
  2. Upgrade to 17.4.4, 17.3.10, 16.0.49 or later and complete the database upgrade step; servers on other release lines must move to one of these.
  3. If you cannot upgrade today, disable public surveys and block survey-context requests to the root dispatcher, DataImportController and ParcelController as temporary containment.
  4. Before upgrading, preserve web server, proxy and application logs and a copy of the REDCap files so you can investigate afterwards.
  5. If you find signs of compromise, treat the server as fully compromised: rebuild from trusted files, rotate credentials stored on it and start your data-breach process.

How to check if you are affected or compromised

  • Search access logs for survey requests with an encoded __passthru value (for example %2569ndex.php) or the routes DataImportController:index and ParcelController:show.
  • Look for Data Import requests whose fname value contains a URI scheme or php://filter chain; request bodies are often not logged, so a clean search is not proof.
  • Check the REDCap temp/cache directory for unexpected changes to compiled templates and compare application files against a trusted backup.
  • Review process logs or EDR telemetry for child processes started by the PHP or web server account.

What happened#

On November 18, 2026, CISA added CVE-2026-90817 to its Known Exploited Vulnerabilities catalog, which means it has evidence of exploitation. The flaw is in REDCap, Vanderbilt University's web application for research surveys and study databases. The CVE record, published September 20 by Securifera, scores it 9.8 and describes unauthenticated remote code execution through survey passthrough routing and Data Import processing. The KEV entry gives federal agencies until November 21, three days, and marks it as requiring forensic triage under BOD 26-04. CISA has not said who is exploiting it or against whom, and lists ransomware use as unknown.

Securifera researcher Ryan Wincey, who found the bug, published a full walkthrough on September 27. The public survey page has a passthrough feature meant to reach only a PDF route. A double-encoded value such as %2569ndex.php passes the allowlist but skips the route restriction, so a survey request can reach any controller. REDCap computes user rights before it sets the survey respondent identity, and an undefined super-user flag yields full rights. The public request therefore gets the Data Import privilege, and CSRF checks are skipped. Data Import then trusts the fname parameter as a file path or PHP stream such as php://filter, and writes data back to it. Wincey used that to overwrite a compiled template cache file, which REDCap executes as PHP when it renders a public page.

Who is affected#

The CVE record lists 13.3.0 as affected and 16.0.49, 17.3.10 and 17.4.4 as unaffected. According to the community REDCap Knowledge Base, those three builds shipped on September 9, 2026, as a critical fix for the Standard line and both LTS lines. No fixed build is listed for other lines, such as 16.1.x or 17.0 through 17.2, so those servers must move to a fixed line. REDCap is not openly distributed. Securifera notes that it is provided to consortium members, and the REDCap Community, where Vanderbilt posts announcements, requires an administrator login. Vanderbilt's own notice was not public as of November 19, 2026.

Exposure is broad and patching is slow. Censys counted just over 8,500 internet-facing REDCap instances in June 2026, 40% of them in the US. A single build, 16.0.17, accounted for 30.1% of what it saw. SecurityWeek reported that only about 1% ran the latest release.

Do you really need to act?#

Yes, if you run REDCap. The one precondition, a valid public survey hash, is not a secret. It appears in every public survey link, and Wincey notes that such links are easy to find through search engines, urlscan and the Wayback Machine. After that, he writes, the steps are "remote, deterministic, and require no user interaction." CISA's own scoring in the CVE record marks the flaw as automatable with total technical impact. The technique has been public since September, and Dataminr reports a public proof of concept on GitHub.

REDCap servers hold research and often clinical data, and they have been targeted before. SecurityWeek, citing Google's threat intelligence group, reports that a group tracked as UNC6508 has breached REDCap servers at US research organizations since 2023, though that campaign has not been tied to this CVE.

Turning off public surveys helps but is not a fix. Ostorlab notes it removes the analyzed entry point but leaves the rights calculation and the Data Import write unchanged.

What to do now#

  1. Inventory every REDCap server, including those run by departments, labs or affiliates outside central IT. Check the version on the Control Center home page, or list the versioned code directories on the server, for example ls -d /var/www/html/redcap/redcap_v*.
  2. Upgrade to 17.4.4, 17.3.10, 16.0.49 or later and finish the database upgrade step. Servers on other release lines need to move to one of these.
  3. If you cannot upgrade today, follow Securifera's containment advice: restrict or disable public surveys, and block survey-context access to the root dispatcher, DataImportController and ParcelController. Remove these measures only after upgrading.
  4. Before upgrading, preserve web, proxy and application logs and a copy of the REDCap files for investigation.
  5. If you find evidence of compromise, treat the whole server as compromised: rebuild from trusted files, rotate credentials stored on it, and start your breach process for the study data it holds.

How to tell if you were hit#

Securifera lists what to look for: encoded __passthru values, survey requests to DataImportController:index or ParcelController:show, fname values containing URI schemes or conversion filters, unexpected changes under temp/cache, and child processes launched by the PHP or web server account. A first pass is grep -E '__passthru=%25|DataImportController|ParcelController' /var/log/apache2/access.log*, adjusted for your server and log path. Attackers can vary the encoding, and fname travels in the POST body, which is usually not logged, so a clean search is not proof. Ostorlab also suggests comparing application and template cache files against a trusted backup. CISA has published no indicators of compromise, and none were disclosed as of November 19, 2026.

Timeline#

  • — REDCap 17.4.4, 17.3.10 and 16.0.49 ship with the fix, per the REDCap Knowledge Base.
  • — Securifera publishes CVE-2026-90817 (CVSS 3.1 9.8).
  • — Securifera publishes the technical walkthrough of the exploit chain.
  • — CISA adds CVE-2026-90817 to KEV with a November 21 due date and a forensic triage requirement.

Vulnerability records

  • CVE-2026-90817 · KEV 2026-11-18 · An unauthenticated Remote Code Execution vulnerability was found in the survey passthrough routing and Data Import processing logic, in which a malicious user…

Sources

Original sources first: vendor and project advisories, CVE and government records, the discoverers’ write-ups. Every claim above links to one of these. See how the Security Desk works.

Original and primary sources

  1. Securifera — Survey Says…. Remote Code Execution: CVE-2026-90817 securifera.com
  2. CVE record — CVE-2026-90817 cve.org
  3. CISA — CISA Adds Four Known Exploited Vulnerabilities to Catalog (Nov 18, 2026) cisa.gov
  4. CISA — Known Exploited Vulnerabilities catalog entry for CVE-2026-90817 cisa.gov
  5. Securifera — Advisories securifera.com
  6. Project REDCap — Community (consortium login required) projectredcap.org
  7. REDCap Knowledge Base (community) — REDCap Versions, Release Lines and Patching bdeveer.github.io
  8. Censys — REDCap on the Internet: An Exposure Analysis censys.com
  9. Ostorlab — REDCap Unauthenticated RCE, Exploited in the Wild (CVE-2026-90817) blog.ostorlab.co
  10. Dataminr — Unauthenticated RCE Hits REDCap: CVE-2026-90817 Explained dataminr.com
  11. SecurityOnline — CISA Adds 4 Exploited Flaws to KEV: Synology DSM, LiteLLM securityonline.info

Coverage and analysis

  1. SecurityWeek — Majority of Internet-Accessible REDCap Servers Outdated securityweek.com