Threat feed

CVE-2026-90817 — REDCap unauthenticated code execution through public surveys, exploited in the wild: explainer and what universities, hospitals and research institutes should do (listed in KEV, due 21 November)

CVE-2026-90817: unauthenticated code execution in REDCap via public surveys (CVSS 9.8). In KEV 18 Nov. Fixed in 16.0.49, 17.3.10, 17.4.4.

Published 2026-11-19 Updated 2026-11-19 Last verified 2026-11-19 6 min read
On this page

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 ↓
  1. Check your REDCap version
  2. Find REDCap servers central IT does not know about
  3. Update, and review public survey exposure
1 more
  1. 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

1

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).

2

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.

3

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.

4

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

Advisory summary — ADVISORY / KEV
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
9.8
CVSS v3.1
Nov 21
KEV due date (3 days after adding)
13.3.0+
Affected per the CVE record
3 lines
Fixes: 16.0.49, 17.3.10, 17.4.4
  • 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

ItemContentStatus
The flawUnauthenticated code execution via survey routing and Data ImportConfirmed (CVE record)
Affected and fixed versions13.3.0 and higher; fixed in 16.0.49, 17.3.10, 17.4.4Confirmed (CVE record)
ExploitationAdded to KEV; SSVC exploitation active, automatable yesExploitation confirmed (CISA)
Attack method and victimsNot in official sourcesNot stated
Official REDCap announcementCommunity site needs a login; not checked by usUnder investigation

Sources

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.

Latest breaking reports

All breaking reports →

FAQ

QWhat is CVE-2026-90817?
A

An unauthenticated remote code execution flaw in REDCap's survey passthrough routing and Data Import processing. Per the CVE record, 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 can execute arbitrary code on the REDCap server. A valid public survey hash is required. CVSS v3.1 is 9.8.

QWhich versions are affected and what is the fix?
A

The CVE record says the flaw exists in REDCap 13.3.0 and higher. Fixed versions are 16.0.49 (LTS), 17.3.10 (LTS) and 17.4.4 (Standard Release); upgrade to the one for your branch. The record does not name an upper bound, so treat any version from 13.3.0 that is older than the fixed version for its line as affected.

QWho should check?
A

IT departments of universities, hospitals and research institutes that run REDCap, and administrators of REDCap servers that individual labs or clinics set up on their own. REDCap is used worldwide, including in Japan, to collect research data and surveys. The more you rely on public surveys that outside respondents fill in, the closer the entry point is.

QIs it being exploited?
A

CISA added it to KEV on 18 November 2026, due 21 November, with Forensic Triage marked Yes. Ransomware use is Unknown. We could not read the official REDCap community page the KEV note points to. The official sources we could read give no detail about the attacks.

QIs there a workaround if I cannot update yet?
A

The official sources we could read do not describe a workaround that replaces updating. In this site's view, closing public surveys you do not need and putting the REDCap server behind the campus network or a VPN reduces who can reach it. But public surveys exist for outside respondents, so updating is the premise.