Exploited CVEs / Ivanti / CVE-2023-46805

CVE-2023-46805

Ivanti Connect Secure and Policy Secure Authentication Bypass Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted, and the vulnerability is known to be used in ransomware campaigns. Federal agencies were required to remediate by 2024-01-22 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Ivanti Security Advisories, linked below.

Risk summary

HighCISA KEVRansomware
8.2
CVSS v3 base
100%
EPSS exploit probability
High
Severity
2024-01-10
Added to KEV
2024-01-22 (past due)
CISA due date

Actively exploited Ivanti Connect Secure and Policy Secure vulnerability, High severity, CVSS v3 8.2. Added to the CISA KEV catalog 2024-01-10.

Senserva AI read on CVE-2023-46805CISA required actionOfficial fix for CVE-2023-46805Admin questions

Senserva AI Opinion for CVE-2023-46805

The authentication bypass half of the Ivanti Connect Secure zero-day pair that opened 2024: it lets attackers slip past control checks in the web component, and chained with the CVE-2024-21887 command injection it gave unauthenticated code execution on VPN gateways worldwide. The campaign was severe enough that CISA ordered emergency disconnections of federal appliances. EPSS is 100 percent and ransomware use followed the initial espionage wave.

Do this: Confirm every Ivanti Connect Secure or Policy Secure appliance was rebuilt on fixed firmware after the January 2024 campaign, not just patched over a possible compromise.

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

Senserva AI Opinion and rich prompt for CVE-2023-46805

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

Patch immediately
Exploited in the wild and used in ransomware campaigns.
The fix ships from the vendor: Ivanti Security Advisories.
Do this now: Move this ahead of everything else in the queue, then verify the fix actually landed on every exposed device.

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

Full tracking and change history for CVE-2023-46805

Published
2024-01-10
Last revised
2024-01-10
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
  • 2024-01-10 added to the CISA KEV catalog by CISA
  • 2026-07-17 CVSS 0.0 to 8.2; EPSS first scored at 100.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: 2024-01-22 (past due).

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Official fix for CVE-2023-46805

The authoritative fix and affected-version list are published by the vendor. Find the Connect Secure and Policy Secure advisory on Ivanti Security Advisories.

Common questions about CVE-2023-46805

Is CVE-2023-46805 actively exploited?

Yes. CVE-2023-46805 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2024-01-10, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 100%. CISA also reports it is known to be used in ransomware campaigns.

What is the CISA deadline and required action for CVE-2023-46805?

CISA set the federal (BOD 22-01) remediation due date at 2024-01-22, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

What fixes CVE-2023-46805?

The authoritative fix is in the vendor advisory: see Ivanti Security Advisories for the patched Connect Secure and Policy Secure 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-2023-46805?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2023-46805'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 once a day (early morning 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.