CVE-2026-21223
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 · uneditedImproper privilege management 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 confidenceThis is a local privilege management vulnerability in Microsoft Edge (Chromium-based) where an authorized attacker can bypass a security feature. The issue stems from improper handling of privileges within the browser's security model, allowing a user with existing access to escalate or circumvent intended restrictions.
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< 144.0.3719.82CVSS 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Microsoft Edge Chromium versionOpen Microsoft Edge, navigate to edge://settings/help, or run 'msedge --version' from command lineAffected if version shown is below 144.0.3719.82
-
Confirm Edge channel and update statusNavigate to edge://settings/about to see if updates are available and which channel (Stable, Beta, Dev) is in useAffected if update status shows version below 144.0.3719.82 or update is not applied
-
Check for group policy configurationsReview Microsoft Edge group policies under Computer Configuration > Administrative Templates > Microsoft Edge in Group Policy Editor (gpedit.msc)Affected if policies related to privilege or security feature management are configured in a way that could be bypassed (specific policy names not provided in CVE data)
Your environment is affected if Microsoft Edge Chromium version is below 144.0.3719.82 and privilege management features are in use that could be bypassed.
Generated from the published advisory. Verify against your own configuration.
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 · scoped144.0.3719.82
Apply Microsoft Edge security updates when available; until then, limit local user privileges and monitor for suspicious browser behavior or extensions.
144.0.3719.82 or later
- Open Microsoft Edge browser
- Click the Settings and more (three dots) menu in the top-right corner
- Select 'Settings' from the dropdown menu
- In the left sidebar, click 'Help and feedback'
- Click 'About Microsoft Edge'
- The browser will automatically check for updates and display the current version
- If an update is available, click 'Download and install' to update to version 144.0.3719.82 or later
- Restart the browser after the update completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21223 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-21223 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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