What changed
The exploitation listing changes the response priority
CISA added CVE-2026-90817 to its Known Exploited Vulnerabilities catalog on 18 November. The flaw was disclosed earlier by Securifera. Its reported path starts in REDCap's public survey passthrough, reaches an unintended controller route and uses Data Import handling to run code on the server. An attacker does not need a REDCap account, but CISA and the discoverer say a valid public survey hash is required.
That distinction matters. The existence of a public survey alone does not prove an instance was compromised, while the hash is not equivalent to an authenticated administrator session. The affected service may also hold research data and trusted integrations, making server compromise a broader investigation than one malformed request.
A survey hash is a real precondition
Defender workflow
Upgrade, then look at the route boundary
- 1
Confirm the running REDCap release. Inventory production and research instances and apply the latest vendor-supported security release. Confirm the active application build after the change.
- 2
Review public survey exposure. List active survey links and the hosts serving them. If an immediate update is impossible, use the discoverer's temporary restrictions on public surveys and survey-context access to administrative controllers.
- 3
Investigate suspicious requests. Look for unusual survey passthrough and Data Import requests, unexpected changes in compiled template caches and child processes launched by the PHP or web-server account.
Defender note
Follow the trust boundary, not just the URL
The failure is a chain: a survey request crossed a routing boundary, then reached file handling that could affect executable cache content. Review access logs and server changes together. A single blocked request may be scanning; altered cache files or unexpected server processes need a fuller incident response.