# REDCap public survey flaw CVE-2026-90817 added to KEV

Canonical: https://www.oktsec.com/radar/redcap-public-survey-cve-2026-90817
Publisher: Oktsec
Language: en
Published: 2026-11-18T21:03:37Z
Updated: 2026-11-18T21:03:37Z
Record reviewed: 2026-11-18T21:03:37Z
Latest evidence check: 2026-11-18T21:03:37Z
Disclosed: 2026-09-20

CISA added this REDCap flaw to KEV on November 18. An attacker who knows a valid public survey identifier can reach vulnerable processing without an authenticated account.

## Evidence and response priority

- Category: Vulnerability
- Oktsec priority: Act now
- Rationale: CISA lists exploitation. A valid public survey identifier is required, but a user account is not.
- Evidence: Attacks confirmed
- Verification: Multiple sources
- Fix status: Fix available
- Exposure requirement: Application or configuration dependent
- Vendor: Vanderbilt University
- Products: REDCap
- CVEs: CVE-2026-90817

## Technical overview

The assigning CNA identifies 13.3.0 as affected and lists 16.0.49, 17.3.10 and 17.4.4 as unaffected releases. Confirm the correct update path for the local branch. The KEV listing establishes exploitation of this flaw without identifying particular research institutions or datasets.

## Recommended response

Identify public survey servers and confirm the corrected build for the installed branch with the consortium. Restrict access to vulnerable surveys until the server is updated.

Relevant to: Identify REDCap servers hosting public surveys and record the deployed branch and build.

## CVE attribution

- CVE-2026-90817: Vanderbilt University — REDCap. [Source](https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/90xxx/CVE-2026-90817.json)

## CISA KEV evidence

Catalog: 2026.11.18
Checked: 2026-11-18T21:06:31.057Z

### [CVE-2026-90817](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-90817)

- Added: 2026-11-18
- Ransomware use: Not confirmed by CISA
- Federal due date: 2026-11-21
- Federal forensic triage: Yes

Action specified by CISA: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CISA KEV inclusion establishes known exploitation of the listed CVE, not compromise of your environment. Absence does not rule out exploitation. The date added is not the first attack date. Federal deadlines and forensic triage requirements are context, not universal obligations for private organizations or businesses in Latin America.

## Supporting evidence

Snapshot checked: 2026-11-19T21:12:22.272Z. These dates do not change the incident’s editorial review date.

### FIRST EPSS forecast

- [CVE-2026-90817](https://api.first.org/data/v1/epss?cve=CVE-2026-90817): 25.19% probability of observed exploitation in the next 30 days; percentile 97.97%; score date 2026-11-19.

EPSS is a prediction, not exploitation evidence or organization-specific risk. Confirmed exploitation takes precedence. A missing score is not zero. Check status: available; last successful check: 2026-11-19T21:12:22.272Z.

## Response checklist

1. **Locate public surveys** — Identify REDCap servers hosting public surveys and record the deployed branch and build.
2. **Verify the release** — Use the consortium support channel to confirm the correct build for the installation and verify it after deployment.
3. **Check survey activity** — Review application and web server logs for unusual survey and import activity while the server was exposed.

## Relevance to AI environments

Review application and web server logs for unusual survey and import activity while the server was exposed.

## Sources

- [CNA record with prerequisites and version entries](https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/90xxx/CVE-2026-90817.json) — Securifera; Research report; checked 2026-11-18T21:03:37Z
- [Community support for consortium partners](https://projectredcap.org/resources/community/) — REDCap Consortium; Vendor notice; checked 2026-11-18T21:03:37Z
- [Known Exploited Vulnerabilities catalog, November 18](https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json) — CISA; Government advisory; checked 2026-11-18T21:03:37Z

## Editorial record

- 2026-11-18T21:03:37Z: Added the November 18 KEV listing and the applicable response.

## Use this advisory in Radar

Use the Advisory view to understand the issue and its evidence, Affected systems to compare versions, and Response plan to record applicability, an owner and action progress. Plans are saved only in the current browser and can be downloaded for sharing; they are not a shared team account or an automated scan. Completing a plan does not validate remediation. Talk to Oktsec opens a technical consultation with the advisory and selected service preserved. Scope, fees and access are agreed before any assessment.

[Open advisory](https://www.oktsec.com/radar/redcap-public-survey-cve-2026-90817) · [Build a response plan](https://www.oktsec.com/radar/redcap-public-survey-cve-2026-90817#review-workspace)

- [Exposure check consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=redcap-public-survey-cve-2026-90817&service=exposure_check)
- [Patch verification consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=redcap-public-survey-cve-2026-90817&service=patch_verification)

## Scope and corrections

Radar is a selected editorial collection, not a complete vulnerability database or a scan of your environment. Priorities are Oktsec analysis. Source confirmation and checklist completion do not establish whether your systems are compromised or secure.

[Sources and methodology](https://www.oktsec.com/radar/about). Report corrections with supporting sources to info@oktsec.com. Do not send secrets or private incident data.

