LiveActive security incident?Get immediate response
CVE Record

CVE-2023-36887: Microsoft Edge (Chromium-based) Remote Code Execution Vulnerability

Microsoft Edge (Chromium-based) Remote Code Execution Vulnerability

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a high-severity remote code execution issue in Microsoft Edge (Chromium-based). The CVSS data indicates a victim must interact with something, but no privileges are needed. A successful attack could let code run with serious confidentiality, integrity, and availability impact. No provided source confirms active exploitation.

Executive priority

Prioritize remediation in normal high-severity patch cycles, faster for privileged workstations or update-lagging fleets. The impact is severe, but supplied evidence does not show active exploitation.

Technical view

CVE-2023-36887 is listed as a CWE-843 type-confusion remote code execution vulnerability in Microsoft Edge (Chromium-based). CVSS 3.1 score is 7.8 with local attack vector, low complexity, no privileges required, and user interaction required. Microsoft indicates an official fix exists, but the bundle does not provide exact fixed versions.

Likely exposure

Organizations with Microsoft Edge (Chromium-based) deployed on desktops or servers are potentially exposed, especially where browser updates are delayed. The source bundle names version 1.0.0 but provides limited affected-version detail, so confirm exposure through Microsoft’s advisory and fleet inventory.

Exploitation context

The bundle reports no CISA KEV listing and CVSS exploit maturity is unproven. Treat this as a serious browser RCE risk, but do not assume active exploitation from the supplied evidence.

Researcher notes

Key uncertainty is affected-version precision. The bundle lists Edge Chromium-based and version 1.0.0, while Microsoft’s advisory should be treated as authoritative for release applicability and fixed builds. Avoid inferring exploitability beyond the CVSS vector and linked advisories.

Mitigation direction

  • Review Microsoft’s advisory for affected and fixed Edge releases.
  • Update Microsoft Edge through the official Microsoft channel.
  • Confirm enterprise update policies are not pinning vulnerable Edge builds.
  • Prioritize managed endpoints used for privileged administration.
  • Monitor vendor guidance for any revised affected-version details.

Validation and detection

  • Inventory installed Microsoft Edge versions across managed endpoints.
  • Compare installed versions with Microsoft’s CVE-2023-36887 guidance.
  • Verify Edge update policy and update telemetry show successful rollout.
  • Check vulnerability management tools for CVE-2023-36887 detections.
  • Document any systems excluded from automatic browser updates.
Prepared
Confidence
medium
Sources
4

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 · low confidence lookup

CWE-843: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-36887 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
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/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
0Timeline events
0ADP providers
3Source links

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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2023-36887Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/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
Affected products

Products and packages named in the record

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

CWE details

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

CWE-843 · source CWE mapping

Access of Resource Using Incompatible Type ('Type Confusion')

Access of Resource Using Incompatible Type ('Type Confusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.