Edge ChromiumWeb browser · Microsoft

CVE-2025-21279

HIGH · 8.8 CVSS v3.1 Published 2025-02-06
Fix available
A fix is available. Upgrade to 133.0.3065.51 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Microsoft Edge (Chromium-based) Remote Code Execution Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Remote Code Execution vulnerability in Microsoft Edge (Chromium-based) with a CVSS score of 8.8 (HIGH). RCE vulnerabilities allow an attacker to execute arbitrary code on the affected system through the browser, potentially leading to complete system compromise.

MitigationApply the available Microsoft Edge security update or upgrade to the latest patched version of Microsoft Edge.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Edge ChromiumWeb browser
Affected:< 133.0.3065.51

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Microsoft Edge version
    Open Microsoft Edge, click the three-dot menu, go to Settings > About Microsoft Edge, or type edge://settings/help in the address bar to view the version number
    Affected if The displayed version is lower than 133.0.3065.51
  2. Check version via command line
    Open Command Prompt or PowerShell and run: msedge --version
    Affected if The command output shows a version number lower than 133.0.3065.51
  3. Verify Edge update status
    Go to Settings > About Microsoft Edge and check if the browser indicates it is up to date or if updates are available
    Affected if The browser reports being out of date or shows an update is available

You are affected if your Microsoft Edge Chromium version is below 133.0.3065.51, as this is the first version containing the fix for this RCE vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 133.0.3065.51 or later
Fixed in 133.0.3065.51
Interim mitigation

Apply the available Microsoft Edge security update or upgrade to the latest patched version of Microsoft Edge.

Recommended fix High confidence

133.0.3065.51 or later

  1. Open Microsoft Edge browser
  2. Click the three-dot menu (Settings and more) in the top-right corner
  3. Select 'Settings' from the dropdown menu
  4. Click on 'Help and feedback' in the left sidebar
  5. Select 'About Microsoft Edge'
  6. The browser will automatically check for updates and download the latest version
  7. Wait for the update to download and install
  8. Restart Microsoft Edge to complete the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Edge Chromium Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-21279 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-21279 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data