CISA added REDCap’s CVE-2026-90817 to its Known Exploited Vulnerabilities catalog on November 18. The research-data application has a server code-execution flaw reachable through a public survey. Administrators should verify the repaired release for their deployed branch and investigate earlier exposure.
The full CVE record was first published September 20. November 18 is the catalog-addition date, not the vulnerability’s disclosure date or the start of attacks.
A public survey can reach an unintended import route
The advisory describes a routing error that lets an unauthenticated request reach an unintended controller from a public survey. A second weakness in data-import processing allows a supplied file path or stream parameter to lead to code execution on the server.
The attacker must know a valid public survey hash, the identifier used to reach that survey. An account is unnecessary. The advisory says the flaw exists in REDCap 13.3.0 and higher, with the repaired releases below excluded. It supplies no complete matrix of every intervening release.
The risk concerns the server running REDCap, not merely a survey response. These sources do not identify particular institutions, stolen datasets or a measured number of compromised installations.
Evidence status: exploitation reported by CISA. The CVE record’s CISA assessment marks exploitation as active. The public catalog provides no campaign account, attacker attribution or first-exploitation timestamp. Its ransomware-use field is Unknown.
Check the release line before calling the repair complete
The CVE’s issuing organization, Securifera, names these repairs:
| Deployed release line | Named repaired release |
|---|---|
| 16.0 long-term support | 16.0.49 LTS |
| 17.3 long-term support | 17.3.10 LTS |
| Standard release | 17.4.4 |
Use the appropriate supported release or its subsequently maintained successor. A higher-looking version on a different branch is insufficient evidence that the repair is included.
REDCap’s Community site holds software downloads and technical support for registered administrators. An end-user project account does not grant access to that maintenance channel. Researchers using a hosted institutional instance should ask its administrator to confirm the deployed branch and completed update.
Preserve evidence alongside the update
CISA’s catalog entry flags this vulnerability for forensic triage, an initial investigation of possible compromise. It lists November 21 as the due date. That federal compliance context is governed by BOD 26-04, including assessment of asset exposure; it is not a universal deadline for every research institution.
For operators, the supported sequence is:
- Identify the affected installation and its public-survey exposure. Use deployment records and administrator documentation to establish branch and patch status.
- Preserve relevant evidence before changes erase it where feasible. CISA’s triage guidance calls for collecting necessary volatile evidence and persistent records before critical patching.
- Coordinate containment and installation of the appropriate repair. Verify the running application after the update, not just the downloaded package.
- Investigate unauthorized access, persistence and possible data removal. These are general triage questions from CISA’s guidance, not campaign-specific detection indicators.
A completed patch closes the documented route. It cannot establish that an earlier reachable installation was never compromised.
Caveat: Vendor release notes require administrator access; the exact repair versions above come from Securifera’s public CVE advisory. Securifera sells security assessment services.