CVE-2026-90817
How to tell if CVE-2026-90817 (REDCap) is reachable in your environment
Reachable if a REDCap server on 13.3.0 or later without a fixed build (16.0.49 LTS, 17.3.10 LTS or 17.4.4 Standard) can be reached over the network and has a public survey live. No login is needed
Attackers were already inside REDCap servers in October, so upgrading now stops new attacks but does not tell you whether yours was hit. Unit 42 reported on October 7, 2026 that attackers used CVE-2026-90817 against public-facing REDCap servers, planted a web shell and ran a cryptocurrency miner. CISA added it to the Known Exploited Vulnerabilities catalog on November 18, with a due date of November 21.
The flaw lets someone with no login run code on a REDCap server, as long as they know the link to one of its public surveys. It affects REDCap 13.3.0 and later. Securifera, which found it and issued the CVE, rates it 9.8 Critical. The CVE record lists the fixed builds as 16.0.49 LTS, 17.3.10 LTS and 17.4.4 Standard Release. Unit 42 quotes REDCap as saying it shipped the fix within two days of learning about the flaw in September.
Universities, hospitals and research groups run REDCap, often outside central IT, and many instances hold study and patient data.
Is it reachable for you?
What it is. The CVE record says a request sent from a public survey can reach a part of REDCap that should not be reachable from there, and a crafted file reference in the data import step then runs code on the server. No login is needed, but the attacker needs a valid public survey link. Securifera notes those links are meant to be shared openly and are often easy to find.
Who is most exposed. Any internet-facing REDCap server on an affected build with at least one public survey turned on. Lab and department installs that central IT doesn't manage are the usual blind spot.
Checks, in three tiers. The first two decide exposure. The third decides priority. Run these only on systems your organization owns.
- Which REDCap versions run? Find every REDCap instance and read its version. 13.3.0 and later is affected unless it is on 16.0.49 LTS, 17.3.10 LTS, 17.4.4 Standard or later.
- Is a public survey live? List the projects with an active public survey link. If none are live, the precondition in the CVE record isn't met, though links can be turned on again at any time.
- Can untrusted networks reach it? Test whether the REDCap web address answers from the internet. Internet-facing servers with live public surveys go first.
Compensating controls (test them, don't assume them)
Vanderbilt's guidance sits on the administrator-only REDCap Community site, so we could not read any workaround from it. Upgrading to a fixed build is the fix.
- Turn off public surveys you don't need. Securifera, which found the flaw, suggests restricting or disabling public surveys as temporary containment until you can upgrade.
What to look for in logs
Vanderbilt has published no indicators we could read. Unit 42 describes what attackers did on the servers it saw, and these signs come from that report.
- Unexpected files in REDCap's temp or cache folder, where Unit 42 found a disguised web shell.
- A cryptocurrency miner named to look like a system logging service, hidden in a dot-folder under /var/tmp.
- New SSH keys in authorized_keys files, new cron jobs, changes to ~/.profile, and cleared shell history on the web server.
- Outbound connections from the web server to a cryptocurrency mining pool.
FAQ
Am I exposed to CVE-2026-90817?
You are if a REDCap server on 13.3.0 or later without a fixed build can be reached over the network and has a public survey live. No login is needed.
Is CVE-2026-90817 being exploited?
Yes. CISA lists it in KEV (added November 18, 2026, due November 21). Unit 42 reported attackers using it to install a web shell and a cryptocurrency miner on October 7, 2026.
I upgraded after October 7. Does that prove no one got in?
No. Attacks were reported after the fix shipped. Upgrading stops new attempts but does not remove anything already planted. Check the server for the signs Unit 42 describes in the detection section above, and follow your incident response process if you find any.
Where are the official fix notes?
Vanderbilt posts REDCap release notes on its Community site, which only registered REDCap administrators can read. The fixed builds on this page come from the CVE record. Ask your REDCap administrator to confirm.
- Vendor
- Vanderbilt University
- Product
- REDCap research data platform
- Affected versions
- REDCap 13.3.0 and later, per the CVE record. Fixed in 16.0.49 LTS, 17.3.10 LTS and 17.4.4 Standard Release
- Vulnerable component
- Public survey routing and Data Import processing
- CVSS
- 9.8 Critical (Securifera as CNA, CVSS 3.1). NVD has not added its own score
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (Securifera)
- CWE
- CWE-94 and CWE-73 (Securifera)
- Exploitation
- Confirmed (CISA KEV)
- CISA KEV added
- November 17, 2026
- Patch
- REDCap 16.0.49 LTS, 17.3.10 LTS or 17.4.4 Standard Release, or later, per the CVE record. Vanderbilt's own release notes are on the REDCap Community site, which only registered REDCap administrators can read
Updates
Nov 18, 2026. First published. CISA added CVE-2026-90817 to KEV on November 18, due November 21. Unit 42 reported exploitation on October 7.
Sources
- CVE record, CVE-2026-90817 (Securifera as CNA; affected and fixed builds; CISA review lists exploitation as active)
- Unit 42, XMRig campaign through CVE-2026-90817 (Oct 7, 2026)
- Securifera write-up (Sept 27, 2026)
- REDCap Community site (release notes, administrators only; linked from CISA KEV)
- NIST NVD: CVE-2026-90817 (no NVD score, checked Nov 18)
- CISA Known Exploited Vulnerabilities catalog (added Nov 18, 2026, due Nov 21; catalog version 2026.11.18)
We publish an advisory when a vulnerability is Critical or on CISA KEV, has one identifiable component to check, and has a public proof of concept or reported exploitation. Advisories are updated as exploitation status changes.