Skip to main content
CVE-2025-21283VulnerabilityPublished Updated

CVE-2025-21283: Microsoft Edge (Chromium-based) · Insufficient Granularity of Address Regions Protected by Register Locks

Affects Microsoft Edge (Chromium-based)Source CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.4% chance of exploitation in 30 days – higher than 73% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:P/RL:O/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Feb 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Microsoft Microsoft Edge (Chromium-based)Affected
  • =1.0.0.0
Fixed in–

AI-suggested

1. Monitor Microsoft security advisories closely and apply official patches or updates for Microsoft Edge Chromium as soon as they become available to address CVE-2025-21283. 2. Until patches are released, restrict user interaction with untrusted or suspicious web content by implementing browser security policies such as disabling JavaScript or using content filtering solutions. 3. Employ endpoint protection solutions that can detect and block suspicious browser behaviors indicative of exploitation attempts. 4. Educate users about the risks of interacting with unknown links or websites to reduce the likelihood of triggering the vulnerability. 5. Consider deploying network-level protections such as web proxies or secure web gateways that can inspect and block malicious content targeting browser vulnerabilities. 6. Use browser isolation technologies where feasible to contain potential exploitation within a sandboxed environment. 7. Regularly update all software components and dependencies related to the browser to minimize exposure to known vulnerabilities. 8. Conduct internal penetration testing and vulnerability assessments focusing on browser security to identify and remediate similar issues proactively.

Description

Microsoft Edge (Chromium-based) Remote Code Execution Vulnerability

References

Community reviews

Loading reviews…