dbcve.org
Edge ChromiumWeb browser · Microsoft

CVE-2025-47182

MEDIUM · 5.6 CVSS v3.1 Published 2025-07-11
Fix available
A fix is available. Upgrade to 138.0.3351.55 or later.
See remediation →
58/100
Remediation priority · Elevated
Zero-click

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
Improper input validation in Microsoft Edge (Chromium-based) allows an authorized attacker to bypass a security feature locally.

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

Improper input validation in Microsoft Edge (Chromium-based) allows a local, authorized attacker to bypass a security feature. The vulnerability stems from insufficient validation of input data within the browser's security boundaries, enabling a local attacker with existing access to circumvent protection mechanisms.

MitigationApply Microsoft Edge security updates as they become available. Until a patch is released, limit local access to systems running Edge and monitor for unusual browser behavior or configuration changes.

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:< 138.0.3351.55

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
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

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

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. Verify Microsoft Edge is installed
    Check for Edge installation by looking in common locations: Windows: Check 'C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe' or 'C:\Program Files\Microsoft\Edge\Application\msedge.exe'. macOS: Check '/Applications/Microsoft Edge.app'. Linux: Check '/usr/bin/microsoft-edge' or '/opt/microsoft/msedge'. Alternatively, run 'msedge --version' (Windows) or '/Applications/Microsoft\ Edge.app/Contents/MacOS/Microsoft\ Edge --version' (macOS) to get the version directly.
    Affected if Microsoft Edge Chromium-based browser is installed on the system
  2. Determine the installed Edge version
    Run 'msedge --version' in command prompt or PowerShell on Windows, or '/Applications/Microsoft\ Edge.app/Contents/MacOS/Microsoft\ Edge --version' on macOS, or 'microsoft-edge --version' on Linux. This displays the full version number (e.g., 138.0.3351.55).
    Affected if Unable to retrieve a version number indicates Edge may not be the Chromium-based variant or is not properly installed
  3. Compare version against affected range
    Take the version number obtained from the previous step and compare it numerically to 138.0.3351.55. Any version lower than 138.0.3351.55 (e.g., 137.x.x.x, 136.x.x.x) falls within the affected range.
    Affected if Installed version is less than 138.0.3351.55 (e.g., 137.0.1234.56, 136.5.1.2, etc.)
  4. Assess local access environment
    Since this is a local attacker scenario, evaluate who has physical or logged-in access to the system. Check for shared workstations, multiple user accounts with local administrative rights, or systems where remote desktop/team viewer is enabled. Review Windows Event Logs for multiple failed logins or unusual session activity.
    Affected if System has multiple local users, shared access, or weak access controls allowing unauthorized local access to an authenticated session

A system is affected if Microsoft Edge Chromium-based browser is installed with a version number lower than 138.0.3351.55 and the system has insufficient local access controls, allowing a local authorized attacker to exploit the improper input validation.

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 138.0.3351.55 or later
Fixed in 138.0.3351.55
Interim mitigation

Apply Microsoft Edge security updates as they become available. Until a patch is released, limit local access to systems running Edge and monitor for unusual browser behavior or configuration changes.

Recommended fix High confidence

Edge Chromium 138.0.3351.55 or later

  1. Open Microsoft Edge and navigate to Settings > Help and feedback > About Microsoft Edge to check the current version
  2. If the version is below 138.0.3351.55, click 'Update Microsoft Edge' to download and install the latest version
  3. Restart the browser after the update completes
  4. Verify the version is now 138.0.3351.55 or later by returning to the About page

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-47182 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