Skip to content

CVE-2023-46805

An authentication bypass vulnerability in the web component of Ivanti ICS 9.x, 22.x and Ivanti Policy Secure allows a remote attacker to access restricted resources by bypassing control checks.

CVSS
8.2Highscored by the publisher (CNA)
Exploited in the wild
Yes, in CISA KEV since 10 Jan 2024CISA deadline for US federal agencies: 22 Jan 2024known use in ransomware campaignspublic exploit code
EPSS
> 99.9%chance of exploitation in the next 30 daystop 0.1% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
12 Jan 2024analysed here 12 Nov 2026

Do first. Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weakness

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Ivanti ICS<= 9.1R18<= 22.6R2Vendor says fixed in: not stated
Ivanti IPS<= 9.1R18<= 22.6R1Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • ivanti:connect_secure
  • ivanti:policy_secure

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. Cloudflare publishes WAF a rule written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.

Also consider: patch · enable the vendor rule in block mode · add auth middleware

Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 10 Jan 2024. Known use in ransomware campaigns.
CISA due date
22 Jan 2024, the remediation deadline for US federal agencies
CISA required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Public exploit code
Yes: 1 Metasploit module · 9 GitHub proofs of concept · 1 Nuclei template
CISA SSVC
exploitation active, automatable yes, technical impact partialAssessed by CISA 1 Oct 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Nuclei

GitHub proofs of concept

and 5 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 10 Jan 2024Added to CISA KEV (exploited in the wild)
  2. 12 Jan 2024Published3 days later
  3. 14 Jan 2024First public exploit or proof of concept1 day later
  4. 22 Jan 2024CISA remediation due date (US federal agencies)8 days later
  5. 1 Oct 2026CISA SSVC assessment: exploitation active984 days (about 3 years) later
  6. 1 Oct 2026CVE record last updatedsame day later
  7. 12 Nov 2026Analysed by vulneraibility.com42 days later

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityLowLimited modification possible.
AvailabilityNoneThe service stays up.

Common questions

Is CVE-2023-46805 being exploited?

Yes. CVE-2023-46805 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2023-46805?

CVE-2023-46805 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2023-46805?

Yes. A fix has been recorded for CVE-2023-46805. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2023-46805 affect?

CVE-2023-46805 affects ivanti:connect_secure, ivanti:policy_secure. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

3 references in the CVE record, grouped by the tags the record gives them.

Other links (3)

  • forums.ivanti.com /s/article/CVE-2023-46805-Authentication-Bypass-CVE-2024-21887-Command-Injection
  • packetstormsecurity.com /files/176668/Ivanti-Connect-Secure-Unauthenticated-Remote-Code-Execution.html
  • cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-46805

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com