REDCap unauthenticated RCE
Actively exploited
Risk assessment
REDCap 13.3.0+ unauthenticated RCE, exploited in the wild (CVSS 9.8). Requires a public survey hash. Upgrade to the latest vendor release now.
What to do
Apply the latest security patches from the vendor. If patching is not immediately possible, review the mitigation steps in this advisory and monitor for exploitation attempts.
- No fixed version listed yet. Restrict exposure and watch the vendor advisory. NVD references
- Remediation and Mitigation in this advisory
Actively exploited in the wild - CVE-2026-90817 is a critical unauthenticated remote code execution flaw in REDCap 13.3.0 and higher that lets an attacker run arbitrary code on the server by abusing public survey routing and crafted Data Import requests. The only barrier to exploitation is knowledge of a valid public survey hash; no login is required.
Overview
REDCap is a widely deployed web application for building and managing research surveys and clinical data capture, common in hospitals, universities, and research consortia. This vulnerability lives in two connected pieces of the application: the routing layer that handles passthrough requests from public survey pages, and the Data Import processing logic that accepts file paths and streams.
An attacker can manipulate HTTP requests to reach a controller route that should only be accessible from an internal, trusted context, rather than from a public survey page. Separately, the import handler accepts a crafted file-path or stream parameter without adequate validation. Chained together, these weaknesses let an unauthenticated attacker execute arbitrary code on the REDCap server.
The CVSS score is 9.8, reflecting a network attack vector, low complexity, no privileges required, and no user interaction. Exploitation does require one piece of knowledge: a valid public survey hash. Because public surveys are designed to be shared with respondents, these hashes are frequently exposed in email links, QR codes, and public web pages, so they should not be treated as a real security control.
Impact
Successful exploitation gives the attacker remote code execution on the REDCap server. Because REDCap stores sensitive research and patient data, a compromised instance can lead to theft, tampering, or exfiltration of study data, and the server can be used as a foothold to pivot further into the network. Given the low complexity and active exploitation, any internet-facing REDCap instance running 13.3.0 or higher should be considered at risk until patched.
Remediation and Mitigation
- Upgrade REDCap to the latest vendor release that addresses CVE-2026-90817 and verify the installed version after upgrading. Consult the official REDCap release notes for the exact fixed version.
- If upgrading immediately is not possible, temporarily disable public survey functionality or restrict survey participation to authenticated users.
- Place REDCap behind a web application firewall or reverse proxy and restrict access to trusted networks where feasible.
- Review the last 30 days of logs for unusual requests to survey passthrough routes and for Data Import calls with unexpected file-path or stream parameters.
- Treat public survey hashes as compromised and rotate them if you suspect exposure.
- If your instance may have been compromised, review system integrity and consult your incident response team. Recent breach reports are available at breach reports and ongoing coverage at security news.
Security Insight
REDCap is a research tool built for openness: public surveys are a core feature designed to be shared widely, and this flaw weaponizes that very accessibility. It is a reminder that “requires a public survey hash” is not an access control but a speed bump, and that the boundary between public-facing survey logic and internal controller routes is exactly where mature applications get breached. Research platforms handling regulated health data deserve the same patch cadence and network segregation as any internet-facing clinical system.
Further Reading
Exploit references 3 PoC · 1 Nuclei Show
Public PoC References
Unverified third-party code
These repositories are publicly listed on GitHub and have not been audited by Yazoul Security. They may contain malware, backdoors, destructive payloads, or operational security risks (telemetry, exfiltration). Treat them as hostile binaries. Inspect source before execution. Run only in isolated, disposable lab environments (offline VM, no credentials, no production data).
Authorized use only. This information is provided for defensive research, detection engineering, and patch validation. Using exploit code against systems you do not own or do not have explicit written permission to test is illegal in most jurisdictions and violates Yazoul's terms of use.
| Repository | Stars |
|---|---|
| murrez/CVE-2026-90817 Unauth REDCap RCE (CVE-2026-90817) mass check PoC — requires public survey hash for full validation. | ★ 2 |
| yulisec/CVE-2026-90817 | ★ 1 |
| securifera/CVE-2026-90817 REDCap DataImport RCE | ★ 1 |
Showing 3 of 3 known references. Source: nomi-sec/PoC-in-GitHub.
Nuclei Detection Templates
Detection template available — your exposure is being scanned
The templates below are YAML signatures for the Nuclei scanner from ProjectDiscovery. They are not exploit code — they are detection rules that confirm whether a target is vulnerable. The presence of a Nuclei template means every bug bounty hunter, AppSec team, red team, and reconnaissance pipeline on the public internet is actively probing for this CVE.
Assume your exposed instances have already been touched. Patch immediately even if no exploitation is observed yet — fingerprinting precedes exploitation by days at most.
| Template | Source |
|---|---|
CVE-2026-90817.yaml | View YAML |
1 Nuclei template indexed for this CVE. Source: projectdiscovery/nuclei-templates.