Secure file handling lessons from REDCap CVE-2026-90817
Secure file handling lessons from REDCap CVE-2026-90817 CVE-2026-90817 shows that a file parameter can cross several trust boundaries before it becomes a code execution primitive. REDCap accepts a client-selected name
Secure file handling lessons from REDCap CVE-2026-90817
CVE-2026-90817 shows that a file parameter can cross several trust boundaries before it becomes a code execution primitive. REDCap accepts a client-selected name during Data Import, reads it through PHP, writes normalized content back to the same resource, and later includes a predictable cache file as PHP.
Vulnerability overview
Securifera reported the flaw and CVE-2026-90817 was assigned. The CVE record gives it CVSS 3.1 9.8 and identifies fixed builds 16.0.49 LTS, 17.3.10 LTS, and 17.4.4 Standard Release. CISA added the issue to its Known Exploited Vulnerabilities Catalog on November 18, 2026, with a November 21 due date for applicable federal organizations.
The affected range starts at REDCap 13.3.0. The vulnerability is a composition of code injection and externally controlled file path behavior, not a simple upload validation warning.
Mechanism and exploitation conditions
The attack starts through a public survey. A double-encoded __passthru value is interpreted differently by the allowlist check and the later route check. That lets the survey context load the root dispatcher with a route such as Data Import. REDCap then creates a user-rights object before the survey respondent identity is established, and the undefined SUPER_USER case returns super-user privileges.
The import path trusts POST[fname] as a local path or PHP stream. It does not require a server-issued upload handle and does not reject stream wrappers. The application reads the selected resource, removes a byte-order mark, and writes the changed content back. Securifera uses a generated php://filter chain to create exact bytes and a removable BOM to force the write.
The write reaches a BladeOne compiled-template cache with a predictable name. When a public Parcel route renders that view, BladeOne includes the cache as PHP. The filter chain is a byte factory; the actual execution sink is the application's include of the modified cache.
Exploitation requires knowledge of a valid public survey hash and no authenticated REDCap account. That fact should change how teams evaluate public survey endpoints and file-processing routes.
Impact
Code runs in the REDCap application's process context. The attacker may be able to read or alter research data, access uploaded documents, use database credentials, and reach internal services. A cache overwrite can also cause availability problems if a payload is partial or the template is left in a broken state.
CISA confirms known exploitation. The reviewed sources do not show which installations were affected or whether data was extracted. Those conclusions require site-specific evidence.
Affected products and scope
Check for REDCap 13.3.0 or later before the appropriate fixed release. The three fixed versions cover different support lines, so maintainers should verify both the installed build and the branch. Public survey availability is a critical scoping attribute because it is the initial route into the vulnerable flow.
Exposure context
ZoomEye Search app="REDCap" returned 22,014 product fingerprints. The Filter query vul.cve="CVE-2026-90817" returned 0. Exposure uses 22,014, the larger selected count. The value does not prove vulnerable software or exploitable configuration; it only counts matching product assets.
Remediation and mitigations
Upgrade to 16.0.49, 17.3.10, 17.4.4, or a later maintained release. If an immediate upgrade is not possible, restrict or disable public surveys and block survey-context access to the root dispatcher, Data Import, and Parcel routes. Preserve suspicious cache files and logs before cleanup.
Application teams should review every file field that accepts a name, path, URI, or stream. Generate server-side upload handles, reject unsupported schemes, use canonical server-controlled paths, and separate validation from later file operations. The fix also needs tests for request decoding differences and routes reached from a public context.
For detection, correlate Data Import requests with encoded passthrough values, fname parameters containing stream syntax, and writes under the REDCap cache. Inspect PHP child processes and outbound connections from the web account. After the patch, verify the build, rotate exposed secrets, and continue review for persistence or data access.
References
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.