Internet Shortcut Files Security Feature Bypass Vulnerability
CVE-2024-21412
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2024-02-13), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.1 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 99.9%
- KEV
- ⚠ Exploited
Published
February 13, 2024
Last Modified
October 28, 2025
Advisory Details (2)
Auto-updated Jun 3, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-21412Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21412Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 84× in last 7d / 382× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 676 total refreshes for this CVE.
- 2026-07-23 02:33 UTCEG score recompute
- 2026-07-22 23:07 UTCEG score recompute
- 2026-07-22 23:07 UTCVendor advisory
- 2026-07-22 23:07 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 19:12 UTCGHSA enrichment
- 2026-07-22 15:18 UTCVendor advisory
- 2026-07-22 15:18 UTCGHSA enrichment
- 2026-07-22 11:23 UTCVendor advisory
- 2026-07-22 11:23 UTCGHSA enrichment
- 2026-07-22 07:30 UTCVendor advisory
- 2026-07-22 07:30 UTCGHSA enrichment
- 2026-07-22 03:35 UTCVendor advisory
- 2026-07-22 03:35 UTCGHSA enrichment
- 2026-07-21 23:38 UTCVendor advisory
- 2026-07-21 23:37 UTCGHSA enrichment
- 2026-07-21 19:01 UTCVendor advisory
- 2026-07-21 19:01 UTCGHSA enrichment
- 2026-07-21 15:07 UTCVendor advisory
- 2026-07-21 15:07 UTCGHSA enrichment
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 11:12 UTCVendor advisory
- 2026-07-21 11:12 UTCGHSA enrichment
- 2026-07-21 07:17 UTCVendor advisory
- 2026-07-21 07:17 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-07-21 03:22 UTCVendor advisory
- 2026-07-21 03:22 UTCGHSA enrichment
- 2026-07-20 23:29 UTCVendor advisory
- 2026-07-20 23:29 UTCGHSA enrichment
- 2026-07-20 19:35 UTCVendor advisory
- 2026-07-20 19:35 UTCGHSA enrichment
- 2026-07-20 15:41 UTCGHSA enrichment
- 2026-07-20 11:47 UTCGHSA enrichment
- 2026-07-20 07:53 UTCVendor advisory
- 2026-07-20 07:53 UTCGHSA enrichment
- 2026-07-20 03:59 UTCVendor advisory
- 2026-07-20 03:59 UTCGHSA enrichment
- 2026-07-20 00:05 UTCVendor advisory
- 2026-07-19 20:10 UTCVendor advisory
- 2026-07-19 20:10 UTCGHSA enrichment
- 2026-07-19 16:16 UTCVendor advisory
- 2026-07-19 16:16 UTCGHSA enrichment
- 2026-07-19 12:22 UTCVendor advisory
- 2026-07-19 12:22 UTCGHSA enrichment
- 2026-07-19 08:29 UTCVendor advisory
- 2026-07-19 08:29 UTCGHSA enrichment
- 2026-07-19 04:35 UTCVendor advisory
- 2026-07-19 04:34 UTCGHSA enrichment
- 2026-07-19 00:40 UTCGHSA enrichment
- 2026-07-18 20:46 UTCVendor advisory
- 2026-07-18 20:46 UTCGHSA enrichment
- 2026-07-18 16:51 UTCVendor advisory
- 2026-07-18 16:51 UTCGHSA enrichment
- 2026-07-18 12:57 UTCVendor advisory
- 2026-07-18 12:57 UTCGHSA enrichment
- 2026-07-18 09:03 UTCVendor advisory
- 2026-07-18 09:03 UTCGHSA enrichment
- 2026-07-18 05:09 UTCVendor advisory
- 2026-07-18 05:09 UTCGHSA enrichment
- 2026-07-18 01:14 UTCVendor advisory
- 2026-07-18 01:14 UTCGHSA enrichment
- 2026-07-17 21:20 UTCVendor advisory
- 2026-07-17 21:20 UTCGHSA enrichment
- 2026-07-17 17:26 UTCVendor advisory
- 2026-07-17 17:26 UTCGHSA enrichment
- 2026-07-17 13:32 UTCVendor advisory
- 2026-07-17 13:32 UTCGHSA enrichment
- 2026-07-17 09:38 UTCEG score recompute
- 2026-07-17 09:38 UTCVendor advisory
- 2026-07-17 09:38 UTCGHSA enrichment
- 2026-07-17 05:44 UTCVendor advisory
- 2026-07-17 05:44 UTCGHSA enrichment
- 2026-07-17 01:50 UTCVendor advisory
- 2026-07-17 01:49 UTCGHSA enrichment
- 2026-07-16 21:55 UTCVendor advisory
- 2026-07-16 21:55 UTCGHSA enrichment
- 2026-07-16 18:01 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 14:07 UTCVendor advisory
- 2026-07-16 14:07 UTCGHSA enrichment
- 2026-07-16 10:13 UTCVendor advisory
- 2026-07-16 10:13 UTCGHSA enrichment
- 2026-07-16 06:18 UTCVendor advisory
- 2026-07-16 06:18 UTCGHSA enrichment
- 2026-07-16 02:24 UTCVendor advisory
- 2026-07-16 02:24 UTCGHSA enrichment
- 2026-07-15 22:30 UTCVendor advisory
- 2026-07-15 22:30 UTCGHSA enrichment
- 2026-07-15 18:36 UTCVendor advisory
- 2026-07-15 18:36 UTCGHSA enrichment
- 2026-07-15 16:49 UTCCISA KEV update
- 2026-07-15 15:04 UTCCISA KEV update
- 2026-07-15 14:41 UTCVendor advisory
- 2026-07-15 14:41 UTCGHSA enrichment
- 2026-07-15 10:46 UTCVendor advisory
- 2026-07-15 10:46 UTCGHSA enrichment
- 2026-07-15 06:52 UTCVendor advisory
- 2026-07-15 06:51 UTCGHSA enrichment
- 2026-07-15 02:57 UTCVendor advisory
- 2026-07-15 02:57 UTCGHSA enrichment
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoClsr00ter/CVE-2024-21412_Water-HydraFirst seen Mar 21, 2024
POC code according to trendmicro's research
Open source ↗
Frequently asked(6)
What is CVE-2024-21412?
When was CVE-2024-21412 disclosed?
Is CVE-2024-21412 actively exploited?
What is the CVSS score of CVE-2024-21412?
Which products are affected by CVE-2024-21412?
How do I remediate CVE-2024-21412?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2024-21412
Is Your Infrastructure Affected by CVE-2024-21412?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.