LiveActive security incident?Get immediate response
CVE Record

CVE-2026-58525: Microsoft Edge (Chromium-based) Security Feature Bypass Vulnerability

Improper access control in Microsoft Edge (Chromium-based) allows an unauthorized attacker to bypass a security feature over a network.

HighCVSS 8.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-58525 is a high-severity Microsoft Edge security feature bypass. An attacker on the network could bypass a browser security control if the user interacts with malicious content. Microsoft has published advisory and patch information. No source provided indicates active exploitation.

Executive priority

Treat this as a near-term browser patching priority. The issue has high potential confidentiality impact, but requires user interaction and has no confirmed active exploitation in the provided sources.

Technical view

The issue is improper access control in Microsoft Edge (Chromium-based), mapped to CWE-284. CVSS 3.1 is 8.2 with network attack vector, low complexity, no privileges required, user interaction required, changed scope, high confidentiality impact, low integrity impact, and no availability impact.

Likely exposure

Organizations using Microsoft Edge (Chromium-based) may be exposed if browsers are not updated according to Microsoft’s advisory. The provided affected-version data is limited, so vulnerability managers should verify applicability directly in MSRC and endpoint inventory.

Exploitation context

The CVSS vector indicates remote network exploitation with user interaction. The source bundle marks KEV as false and exploit maturity as unproven, so active exploitation should not be assumed from the provided evidence.

Researcher notes

Details are sparse beyond Microsoft’s classification and CVSS. The key constraints are UI-required, no privileges required, network vector, and security feature bypass. Do not infer exploitability or affected build ranges beyond Microsoft’s advisory.

Mitigation direction

  • Apply the Microsoft Edge update referenced in the MSRC advisory.
  • Ensure Edge auto-update is enabled and not blocked by policy.
  • Review Microsoft guidance for any additional mitigation or version details.
  • Prioritize managed endpoints where browsers lag behind update baselines.

Validation and detection

  • Inventory Microsoft Edge Chromium-based installations across endpoints.
  • Compare installed versions against the MSRC advisory’s fixed version guidance.
  • Confirm update deployment through endpoint management or vulnerability scanning.
  • Check for policies preventing Edge updates or browser restarts.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-58525 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N/E:U/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N/E:U/RL:O/RC:C2.84.7microsoft

Vulnerability scoring details

Base CVSS 3.1 score

8.2High
CVSS 3.1 vector shape for CVE-2026-58525Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftMicrosoft Edge (Chromium-based)1.0.0.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.