For: IT departments of universities, hospitals and research institutes that run REDCap, and administrators of REDCap servers that labs or clinics run on their own. This article is based on the CVE record and CISA KEV; it does not cover attack steps.
続報待ち:この記事は公式発表に合わせて更新します
- Who is affected
IT departments of universities, hospitals and research institutes that run REDCap, and administrators of REDCap servers that labs or clinics run on their own.
- Confirmed so farSee the table ↓
- The flaw
- Affected and fixed versions
- Exploitation
- Not yet confirmed
- How the attacks work and how far they reached (CISA shows exploitation via KEV and SSVC; no detail in official sources)
- The full text of the official REDCap announcement (the community site needs a login and we could not check it; versions were cross-checked in the CVE record)
- Versions before 13.3.0 and older releases of each line (the CVE record says only 13.3.0 and higher)
- What to do nowSee the steps ↓
- Check your REDCap version
- Find REDCap servers central IT does not know about
- Update, and review public survey exposure
1 more
- Check for signs of abuse
- Where to verify (source)All sources ↓
- CISA KEV
- Last checked
- as of November 19, 2026
Follow-up plans and what we checked
CISA added the flaw to KEV on November 18; its SSVC entry lists Exploitation active, Automatable yes and Technical Impact total. The CVE record was published on September 20, 2026 and credits a researcher at a security firm as the finder.
What to do today
Check your REDCap version
Look up the version in the Control Center or in the version shown at the bottom of REDCap pages. Anything from 13.3.0 that is older than 16.0.49 (LTS), 17.3.10 (LTS) or 17.4.4 (Standard Release) needs an update. Update to the version that matches your line (LTS or Standard).
Find REDCap servers central IT does not know about
Labs and clinics sometimes run their own REDCap server. Search the campus or hospital network for REDCap servers and ask their administrators to update (asset inventory checklist). If you use a vendor-hosted REDCap, ask the vendor whether a fixed version has been applied.
Update, and review public survey exposure
Follow the official REDCap instructions for the update. Also review which projects have public survey URLs on the internet and whether they really need to be public; close those that do not. The public survey hash the attack requires is a value contained in the URL, so review who the URLs have been shared with.
Check for signs of abuse
In web server access logs, look for unfamiliar requests to public survey URLs and to routes related to data import. Also check for unfamiliar files on the server, unusual child processes of the PHP process and outbound connections. If anything looks wrong, isolate the server and assess the affected research data and personal information with your institution's privacy office (how to check for intrusion, hospital cyberattacks and their effect on care).
What kind of flaw this is
- CVE
- CVE-2026-90817 (REDCap: unauthenticated code execution in survey passthrough routing and Data Import processing)
- Severity
- CVSS v3.1 9.8 (critical; AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
- Type
- Code injection (CWE-94), external control of file name or path (CWE-73)
- Impact
- Arbitrary code runs on the REDCap server. No authentication needed, but a valid public survey hash is required
- Affected
- REDCap 13.3.0 and higher (CVE record)
- Fix
- 16.0.49 LTS / 17.3.10 LTS / 17.4.4 Standard Release
- Published
- CVE published September 20, 2026 (last updated November 18). Finder: a security researcher
- Exploitation
- Added to CISA KEV November 18 (due November 21). Ransomware use Unknown, Forensic Triage Yes
- In short: from a public survey entry point, a request reaches processing that should not be reachable, and a value passed to data import is treated as a file location. That ends in server-side code running. Neither the official sources nor this site give how requests are built.
- Public surveys are, by design, open without authentication to outside respondents, so protecting the login alone does not prevent this flaw.
What is known and what is not
| Item | Content | Status |
|---|---|---|
| The flaw | Unauthenticated code execution via survey routing and Data Import | Confirmed (CVE record) |
| Affected and fixed versions | 13.3.0 and higher; fixed in 16.0.49, 17.3.10, 17.4.4 | Confirmed (CVE record) |
| Exploitation | Added to KEV; SSVC exploitation active, automatable yes | Exploitation confirmed (CISA) |
| Attack method and victims | Not in official sources | Not stated |
| Official REDCap announcement | Community site needs a login; not checked by us | Under investigation |
Sources
- CISA KEV — Known Exploited Vulnerabilities Catalog (added November 18, due November 21; the note points to the REDCap community)
- CVE.org — CVE-2026-90817 (published September 20, 2026; affected versions, fixed versions, finder)
- NVD — CVE-2026-90817
- REDCap — REDCap Community (the official channel KEV points to; needs a login, content not checked by us)
- Securifera — Advisories (the finder's advisory list; referenced by the CVE record)
No attack steps are included. Last verified: November 19, 2026.
Update history
2026-11-19: First report. Based on the CVE record and CISA KEV; the fact that the official REDCap announcement could not be checked is listed as unconfirmed.
Read next
- Healthcare readiness: Hospital cyberattacks and their effect on care
- Practice: Vulnerability remediation playbook / Asset inventory checklist
- Prioritizing: Deciding fix order with CVSS, EPSS and KEV
- Term: What RCE (remote code execution) is