A REDCap vulnerability, CVE-2026-90817, is now being exploited, and it lets an attacker with no login run code on the server. CISA added it to its Known Exploited Vulnerabilities catalog on November 18, 2026, with a federal due date of November 21. CISA also marked it as needing forensic triage, which means agencies must check for compromise as well as patch.
REDCap is the survey and research database tool built at Vanderbilt. Universities, academic medical centers, hospitals and research nonprofits run it on their own servers. Many of those servers are managed by a small team in a research office, outside central IT. This post covers what the flaw is, which builds fix it, the stopgap if you cannot upgrade today, how to look for signs of attack, and what to ask your REDCap administrator. Facts are as of November 20, 2026.
The short version: find out who runs each REDCap server your organization uses. Ask them to upgrade today to a build the CVE record lists as not affected: 16.0.49, 17.3.10 or 17.4.4. If that cannot happen today, turn off public surveys or block the routes the researcher names. Then check the logs, because the attack may already have happened.
What the REDCap vulnerability is
The CVE record describes an unauthenticated remote code execution flaw. It sits in two places: the way REDCap routes requests from a public survey, and the way its Data Import tool handles files. The record says an attacker can reach "an unintended controller route from a public survey context." The attacker then supplies a crafted file path during import, which can run code on the server.
The record gives it a CVSS score of 9.8, Critical. The score is that high because the attack works over the network, needs no account and needs no one to click anything. Our guide to reading a CVSS score explains each part of that rating, and our CVE explainer covers the basics.
There is one condition. The attacker needs "knowledge of a valid public survey hash," per the record. That hash is the code at the end of a public survey link. CISA’s KEV entry repeats the same condition.
Why the survey hash is a weak barrier
Public surveys are the normal way REDCap is used. A study team posts a link on a website, in an email or on a flyer. Anyone with the link can open the survey. That same link carries the hash.
Ryan Wincey of Securifera found the flaw and is credited in the CVE record. His September 27 write-up says the hash is "not a password." He adds that survey links are easy to find through search engines, URL scanning services and the Wayback Machine.
According to Securifera, the attack chains five separate bugs. A double-encoded value slips past a route check. A rights check then grants Data Import access to an anonymous survey visitor. Data Import trusts a file name the visitor sends. A cleanup step rewrites that file in place. Finally, a cached template file gets overwritten and then run as PHP code. The write-up calls the remaining steps "remote, deterministic." In plain terms, once an attacker has a link, the rest works the same way every time.
Which REDCap builds fix it
The CVE record lists the REDCap vulnerability as affecting REDCap 13.3.0 and later. It names three builds as not affected.
| Build | Status in the CVE record | What to do |
|---|---|---|
| 13.3.0 up to the fixed builds | Affected | Upgrade today |
| 16.0.49 | Not affected | Confirm this exact build or later on that line |
| 17.3.10 | Not affected | Confirm this exact build or later on that line |
| 17.4.4 | Not affected | Confirm this exact build or later on that line |
| Older than 13.3.0 | Not listed | Out of date anyway; upgrade |
The record, which already named these builds, was published on September 20, 2026. Servers upgraded this fall may already be safe. Servers that were not are the ones at risk now.
We found no public notice about this flaw on Vanderbilt’s project site. Its REDCap Community site requires a partner login, so we could not read it. Your REDCap administrator has access and should confirm the right build there. Vanderbilt’s project site says REDCap is free to nonprofit consortium partners and that partners run their own systems. So each institution patches its own server. There is no central fix that reaches you automatically.
Remove the old REDCap versions too
REDCap lets administrators keep older versions on the server next to the current one. That design came up in a separate case this year. Google Threat Intelligence Group’s June 15 report describes a China-nexus group, UNC6508, that broke into REDCap servers at North American medical and research institutions. Google says it could not confirm how the group first got in. It did see the group "probing for these vulnerable legacy versions."
That campaign is not tied to CVE-2026-90817. Its advice still applies to every REDCap server. Google tells administrators to update to the latest version and "ensure older versions are completely removed." After you patch this REDCap vulnerability, ask whether old version folders are still on the server.
If you cannot upgrade today: the stopgap
Securifera gives two short-term steps for teams that cannot close the REDCap vulnerability with an upgrade right away:
- Restrict or turn off public surveys.
- Block survey-context requests to the root dispatcher, the Data Import controller and the Parcel controller.
The first step will stop active studies from collecting responses. Talk to the study teams before you do it. The second step usually means a rule on a web application firewall or the web server. Your administrator or host will know which is possible. Keep either one in place only until the upgrade is done.
How to check whether the REDCap vulnerability was used
For this REDCap vulnerability, Securifera lists signs to look for in web server logs and on the server itself:
- Requests with encoded
__passthruvalues. - Survey requests that reach
DataImportController:indexorParcelController:show. fnamevalues that contain URI schemes or PHP filter strings.- Unexpected changes to files under
temp/cache. - Programs started by the PHP or web server account.
Google’s June report adds two more checks for the earlier campaign. Look for a web shell named help.php. Scan for the INFINITERED malware with the YARA rule Google published. Its report also lists a session ID prefix to search for in the redcap_sessions table.
If you find signs, assume the attacker could reach anything the REDCap server could. That includes the database, stored study data and any service account passwords in its settings. REDCap often holds health or other sensitive research data. Bring in your security team or incident response provider, and follow your institution’s data incident process.
Our post on the CISA KEV catalog explains how to use KEV listings like this one to set patch order. Our guide to EPSS scores covers how to judge flaws that are not yet on the list.
What to ask your REDCap administrator
At many universities and hospitals, REDCap is run by a research informatics group, a clinical research center or a single developer. It may not be on central IT’s server list at all. Start by finding every REDCap server your organization uses, including ones run by a partner institution or a vendor. Then ask in writing:
- What REDCap build is each server on today? Compare it to the table above.
- When will it be on 16.0.49, 17.3.10, 17.4.4 or later? For this REDCap vulnerability, the answer should be today.
- Are public surveys turned on, and how many are live? If the upgrade must wait, ask whether the stopgap is in place.
- Have the old version folders been removed from the server? Google recommends it after the UNC6508 campaign.
- Did you check the logs for the signs Securifera lists? Ask what they found.
- What PHP version does the server run? REDCap is a PHP application. Our post on the PHP 8.2 end-of-life date covers why that matters this year.
How widespread REDCap is
Vanderbilt’s project site lists 8,547 active partners in 167 countries and more than 4.7 million users, as of November 20, 2026. In June, SecurityWeek reported Censys data showing about 8,500 REDCap instances reachable from the internet. Censys found that just over 1% ran the latest version at that time.
Those numbers do not mean every instance is open to this REDCap vulnerability. They do show how many servers run behind schedule. That makes a one-day KEV deadline hard to meet for most of the sector.
Frequently Asked Questions
What is CVE-2026-90817?
A REDCap vulnerability in survey request routing and Data Import that lets an attacker with no account run code on the server. It is rated CVSS 9.8, Critical.
Is it being exploited?
Yes. CISA added it to the KEV catalog on November 18, 2026, based on evidence of active exploitation. CISA has not said who is behind the attacks.
What is the federal due date?
November 21, 2026, for federal civilian agencies. CISA also marked it as needing forensic triage under BOD 26-04.
Which REDCap builds are safe?
The CVE record lists 16.0.49, 17.3.10 and 17.4.4 as not affected. Builds from 13.3.0 up to those fixes are affected.
Does the attacker need a login?
No. The attacker needs only a valid public survey hash, which is part of any public survey link.
Is there a workaround?
Securifera suggests turning off public surveys or blocking survey access to the Data Import and Parcel controllers until you can upgrade.
Does upgrading remove an attacker who already got in?
No. Check the logs and server files for the signs Securifera lists, and bring in incident response if you find any.
Is this the same as the UNC6508 REDCap campaign?
No. Google reported that campaign in June and could not confirm how the group got in. Its advice to remove old REDCap versions still applies.
Has Vanderbilt published a public notice?
We found none on Vanderbilt’s public project site as of November 20. Its REDCap Community site needs a partner login, and your administrator can check there.