Secuno
ENNL
Book demo

CVE-2025-21399

Microsoft Edge Update vulnerability

7.4 HIGHPublic exploitEPSS 0.68%
  1. Published17 Jan 2025

Description

Microsoft Edge (Chromium-based) Update Elevation of Privilege Vulnerability

CVSS 3.1 breakdown

Attack vectorLocal
Attack complexityHigh
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Microsoft Edge Update< 1.3.195.43

Remediation

Fixed in
Microsoft Edge Update≥ 1.3.195.43

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-592658.8
A code execution issue in the Java integration in Apache OpenOffice v4.1.16 and earlier…
CVE-2026-828628.4
Hulumi versions before v1.3.2 resolve the threat-model helper script from an unsafe…
CVE-2026-781559.9
privilege escalation in StackGres operator allows a low-privilege tenant who owns a…
CVE-2026-748729.8
openssl_encrypt versions before 1.4.0 contain an arbitrary code execution vulnerability…
CVE-2026-166748.8
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to execute…
CVE-2026-483958.6
Bridge is affected by an Untrusted Search Path vulnerability that could result in…

Frequently asked

Is CVE-2025-21399 being actively exploited?

CVE-2025-21399 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.68%.

How severe is CVE-2025-21399?

CVE-2025-21399 has a CVSS 3.1 base score of 7.4, rated high. EPSS estimates a 0.68% probability of exploitation.

Which products are affected by CVE-2025-21399?

Affected products include Microsoft Edge Update.

How do I fix CVE-2025-21399?

Upgrade affected software to a fixed version, for example Microsoft Edge Update 1.3.195.43 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-21399 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.