Exploited CVEs / IBM / CVE-2020-4427

CVE-2020-4427

IBM Data Risk Manager Security Bypass Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2022-05-03 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.

Risk summary

CriticalCISA KEV
9.8
CVSS base
70%
EPSS exploit probability
Critical
Severity
2021-11-03
Added to KEV
2022-05-03 (past due)
CISA due date

Actively exploited IBM Data Risk Manager vulnerability, Critical severity, CVSS 9.8. Added to the CISA KEV catalog 2021-11-03.

Senserva AI read on CVE-2020-4427CISA required actionOfficial fix for CVE-2020-4427Admin questions

Senserva AI Opinion for CVE-2020-4427

CVE-2020-4427 lets a remote attacker bypass authentication in IBM Data Risk Manager by sending a crafted HTTP request when SAML is configured, giving unauthorized access to the appliance. Anyone running this data governance product exposed to reachable networks is at risk, and CISA confirmed active exploitation and added it to KEV on 2021-11-03. With a 70% EPSS score and a CVSS of Critical (9.8), attackers can reach sensitive risk and data-mapping information without valid credentials.

Do this: Apply IBM's fix for Data Risk Manager immediately and restrict network access to the appliance, prioritizing any instance using SAML authentication.

AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2020-4427

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Patch now
Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.
No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.
Do this now: Federal remediation deadline 2022-05-03; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated August 14, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2020-4427

Published
2021-11-03
Last revised
2021-11-03
Changes tracked
1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one
What changed, and when
  • 2021-11-03 added to the CISA KEV catalog by CISA
  • 2026-07-17 CVSS 0.0 to 9.8; EPSS first scored at 70.0%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2022-05-03 (past due).

Apply updates per vendor instructions.

Official fix for CVE-2020-4427

Check the vendor's security advisory channel for the patched Data Risk Manager versions and workarounds.

Common questions about CVE-2020-4427

Is CVE-2020-4427 actively exploited?

Yes. CVE-2020-4427 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 70%.

What is the CISA deadline and required action for CVE-2020-4427?

CISA set the federal (BOD 22-01) remediation due date at 2022-05-03, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply updates per vendor instructions.

What fixes CVE-2020-4427?

Check the vendor's security advisory for the patched Data Risk Manager versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2020-4427?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2020-4427's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.