Actively exploited CVSS 9.8 Security news

REDCap flaw CVE-2026-90817 allows unauthenticated code execution, and CISA now lists it as exploited

On 18 November 2026 CISA added CVE-2026-90817 to its Known Exploited Vulnerabilities (KEV) catalog. The flaw is in REDCap, the platform universities and hospitals use to collect research and clinical trial data. Anyone who knows the link to a single public survey can run code on the server without logging in (CVSS 9.8). The bug has been public since September and fixed versions exist. Palo Alto Networks Unit 42 described a campaign using it to install XMRig cryptominers back in October.

Kyberkit editorial team · · event date · reading time 5 minutes · For admins and analysts

Actively exploited: REDCap, CVE-2026-90817, CVSS 9.8

Key points

  • Who is affected: REDCap installations from 13.3.0 onwards with at least one public survey, which is what the platform is for, so practically all of them.
  • The flaw: public survey routing lets an attacker reach the data import code, where a crafted file path or stream leads to code execution as the web server user (CWE-94).
  • Exploited: yes. CISA has listed it in KEV since 18 Nov 2026, and in October Unit 42 described a campaign dropping the XMRig miner, a web shell and an SSH backdoor.
  • What to do: patch, then check the REDCap cache directory, crontab, authorized_keys files and miner processes. US federal agencies must act by 21 Nov 2026.

Vulnerabilities: CVE-2026-90817

What happened

On 18 November 2026 the US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-90817, a flaw in Vanderbilt University's REDCap, to its Known Exploited Vulnerabilities catalog. US federal agencies have until 21 November 2026 to fix it. That three-day deadline is far shorter than the usual three weeks, and CISA also points agencies to its forensic triage requirements, so it expects them to look for signs of compromise as well as patch.

The bug itself is not new. The NVD record was published on 20 September 2026 by Securifera, the research team that found the flaw, with a CVSS 3.1 score of 9.8. Securifera published a write-up on 27 September. On 7 October Palo Alto Networks Unit 42 described a campaign that exploits internet-facing REDCap servers to install a Monero miner. According to Unit 42, the REDCap team learned of the flaw in September and shipped a fix within two days.

The news, then, is CISA's confirmation of active exploitation. If you have not upgraded REDCap since September, now is the time.

Technical details

REDCap is a PHP web application. Besides logged-in users, it serves public surveys: a study participant gets a link containing a unique survey hash and fills in the form without an account. According to NVD, an attacker who knows a valid hash can abuse the survey passthrough routing to reach code that should not be available to anonymous visitors: the data import handler. There, a crafted file path or stream parameter leads to execution of attacker-supplied code. NVD classifies the issue as code injection (CWE-94) and external control of a file path (CWE-73).

No login or user interaction is needed. The code runs as the web server user (php-fpm in the Unit 42 case), which can read the REDCap configuration and usually the credentials for the database holding the study data.

The campaign Unit 42 described works like this:

How attackers exploit REDCap CVE-2026-90817, according to Unit 421. POST request with a public survey hash; 2. Temporary web shell in the REDCap cache directory; 3. In-memory script fetches the next stage disguised as a JPEG; 4. XMRig miner in a hidden directory, named after syslog; 5. Persistence through crontab, an SSH key and ~/.profile1POST request with a public surveyhash2Temporary web shell in the REDCapcache directory3In-memory script fetches the nextstage disguised as a JPEG4XMRig miner in a hidden directory,named after syslog5Persistence through crontab, an SSHkey and ~/.profile
Attack chain according to Unit 42 (7 Oct 2026)

Unit 42 says the script also kills competing miners, pauses mining while an administrator is logged in and wipes shell history. The added SSH key means the attacker keeps access even after the flaw is patched.

Who is affected

Product Vulnerable Unaffected according to the CVE record
REDCap (Vanderbilt University) 13.3.0 and later, unpatched 16.0.49, 17.3.10, 17.4.4 and later in each branch

At risk are internet-facing installations with at least one public survey. The REDCap team publishes security notes only in its community portal for administrators at partner institutions, so we could only verify the fixed version numbers from the CVE record. Many universities and teaching hospitals run REDCap, and the data in it is often health data, which counts as a special category under the GDPR and is protected by HIPAA in the US.

How to tell if you were compromised

Unit 42 published these indicators (defanged, ready to paste into log searches and EDR):

202.61.130[.]221
39a435123dc1fffd499aa2acf11ef46e3ee2e805bf137811af0c2c5b12546920
/var/www/html/redcap/temp/cache/d3f11fc8ee9c2d986425eff26ecace5b4004eb8e.bladec
/var/tmp/.syslog-a224be51/xmrig.tar.gz
auto.c3pool[.]org
grepb2.jpg
/dev/shm/duet
/var/tmp/.bin

You can parse the indicators and export them for your SIEM with our IOC extractor. Specific IPs and hashes change between campaigns, so look for the general traces too:

  • Unknown files in the REDCap temp/cache directory, especially with a .bladec extension, created when nobody changed the configuration.
  • POST requests to public survey URLs with unusual parameters (file paths, ://, ../) in the web server access log.
  • Child processes of php-fpm or the web server, such as a shell, bash, curl or wget. REDCap does not normally spawn them.
  • High CPU load and processes named like system services (syslog) running from unusual paths, plus connections to mining pools.
  • New crontab entries, new keys in authorized_keys and changes to ~/.profile for the web server user and other accounts.

What to do

  1. Upgrade REDCap to a release the CVE record lists as unaffected (16.0.49, 17.3.10, 17.4.4) or later. Upgrades are available in the projectredcap.org community portal.
  2. Check the server against the indicators above even if it is already patched. The fix does not remove a web shell, cron job or added SSH key.
  3. If you find anything, treat it as a data breach: isolate the server, preserve logs, rotate the database password and any credentials in the REDCap configuration, and assess your notification duties (within 72 hours under the GDPR; HIPAA and state rules in the US).
  4. Reduce exposure: if your public surveys do not need to be open to the whole internet, put REDCap behind a VPN or restrict access by IP address.

Timeline

Timeline of REDCap flaw CVE-2026-90817Sep 2026: REDCap team learns of the flaw and ships a fix within two days (per Unit 42); 20 Sep 2026: CVE-2026-90817 published in NVD by Securifera; 27 Sep 2026: Securifera publishes its write-up; 7 Oct 2026: Unit 42 describes an XMRig mining campaign; 18 Nov 2026: CISA adds the flaw to KEV with a 21 Nov deadlineSep 2026REDCap team learns of theflaw and ships a fix withintwo days (per Unit 42)20 Sep 2026CVE-2026-90817 published inNVD by Securifera27 Sep 2026Securifera publishes itswrite-up7 Oct 2026Unit 42 describes an XMRigmining campaign18 Nov 2026CISA adds the flaw to KEVwith a 21 Nov deadline
From disclosure to the KEV listing (NVD, Securifera, Unit 42, CISA)

Updates

  • 19 Nov 2026: first version.

FAQ

What is REDCap and why should I care?

REDCap (Research Electronic Data Capture) is a web application from Vanderbilt University for collecting data in research and clinical trials. Universities, hospitals and research institutes run it worldwide. The data it holds is often sensitive, such as health information about patients and study participants.

Am I safe if none of my surveys are public?

It lowers the risk, but do not rely on it. According to the CVE description, the attack needs a valid public survey hash, which is the link routinely sent to participants and easily shared further. Patching is the only reliable fix.

Where do I get the fixed version and release notes?

REDCap is not freely downloadable. Upgrades and security notes are published in the projectredcap.org community portal, which is open to administrators at partner institutions. If your IT team or a hosting partner runs REDCap for you, ask them which version you are on.

Sources

  1. CISA – Known Exploited Vulnerabilities Catalog, CVE-2026-90817 (added 18 Nov 2026)
  2. NVD – CVE-2026-90817
  3. Securifera – Survey Says… Remote Code Execution: CVE-2026-90817 (27 Sep 2026)
  4. Palo Alto Networks Unit 42 – XMRig campaign through CVE-2026-90817 (7 Oct 2026)
  5. Project REDCap – community portal for administrators

Spotted a mistake? Let us know and we will correct it openly.