Blog
REDCap CVE-2026-90817: critical code injection exploited
What it is and who is affectedVanderbilt University's Research Electronic Data Capture platform, known as REDCap, carries a code injection flaw tracke...
What it is and who is affected
Vanderbilt University's Research Electronic Data Capture platform, known as REDCap, carries a code injection flaw tracked as CVE-2026-90817. The NVD describes it as an unauthenticated remote code execution issue located in the survey passthrough routing and the Data Import processing logic. An attacker can manipulate HTTP requests to reach an unintended controller route from a public survey context and supply a crafted file-path or stream parameter during import handling, which may allow arbitrary code to run on the REDCap server. No authentication is needed, although the attacker must know a valid public survey hash.

The severity is CVSS 3.1 9.8, critical (vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), and the weakness maps to CWE-73 and CWE-94. It was published in the NVD on 20 September 2026. According to the NVD, the affected versions are REDCap from 13.3.0 inclusive up to 16.0.49 exclusive, from 16.1.0 inclusive up to 17.3.10 exclusive, and from 17.4.0 inclusive up to 17.4.4 exclusive.
REDCap is widely used by research groups, hospitals, universities and clinical trial teams, and in Spain many of these installations sit in public research centres, foundations and healthcare organisations across Catalonia and the rest of the country. If your organisation runs REDCap, or your IT team hosts it for a research department, this concerns you directly.
Why it is urgent
This is not a theoretical flaw. CISA added CVE-2026-90817 to its Known Exploited Vulnerabilities (KEV) catalogue on 18 November 2026, which means it has been observed in real attacks. CISA gave US federal agencies until 21 November 2026 to apply the mitigations indicated by the vendor, in line with its BOD 26-04 guidance on prioritising security updates by risk, and to follow its forensics triage requirements. For cloud deployments, the same guidance applies, or the product should be discontinued if no mitigation is available. The material does not state that this vulnerability has been used in ransomware campaigns.
Even outside the United States, the KEV listing is the clearest signal a small IT team can get: someone, somewhere, is already using this. An unauthenticated remote code execution bug on a server that holds research data, personal data and often GDPR-protected health information is exactly the kind of exposure that turns into a breach notification.
What to do today
- Check whether REDCap is in use and at which version. Compare your installed version against the ranges above. Anything from 13.3.0 up to, but not including, 16.0.49; from 16.1.0 up to 17.3.10; or from 17.4.0 up to 17.4.4 falls inside the affected window.
- Apply the update or mitigation described in the vendor's advisory. The material does not specify which release corrects the flaw, so follow exactly what Vanderbilt's security notice indicates rather than guessing a version number. If no mitigation is available for your deployment, CISA's guidance points to discontinuing use of the product.
- Review for signs of intrusion. Look for unexpected requests hitting controller routes from public survey contexts, unusual file-path or stream parameters in import handling, and any unexpected processes or files on the server. CISA's forensics triage requirements are a useful reference for structuring that review.
- Reduce what is exposed to the internet. CISA explicitly asks asset owners to evaluate each system's internet exposure. Restrict public survey endpoints to what is genuinely needed, and keep administrative interfaces behind a VPN or an allow-list.
- Rotate credentials and survey hashes if you suspect any exposure, and check logs for access from unfamiliar addresses.
How a cybersecurity team such as ALMC's can help
Situations like this one are rarely about a single patch. They are about knowing what you run, which versions are live, and what is reachable from the internet. At ALMC we work with SMEs, online shops and small IT departments in Lleida, Barcelona, Tarragona and Girona on exactly that: security audits and pentesting to find vulnerabilities before someone exploits them, server hardening, monitoring and incident response when something looks wrong, and recovery of websites that have already been compromised.
For organisations running WordPress, PrestaShop or Joomla alongside internal tools such as REDCap, we also handle ongoing maintenance and security patching, so that critical advisories like CVE-2026-90817 do not sit unnoticed in a backlog. The work is unglamorous, but it is what keeps a research platform, an online store or a small company's infrastructure out of the next KEV entry.
Related
- Ivanti Connect Secure: CVE-2026-104935 Under Active Attack
- CVE-2026-96951: Windows Shell Command Injection Under Attack
- Click to Chat for WhatsApp: CVE-2026-92097 in WordPress
- Abuse Shield
Is your business exposed to flaws like this?
ALMC checks which versions you are running, applies the patches and hardens your servers and website. Contact our team for a security review.
