LiveActive security incident?Get immediate response
CVE Record

CVE-2023-36888: Microsoft Edge for Android (Chromium-based) Tampering Vulnerability

Microsoft Edge for Android (Chromium-based) Tampering Vulnerability

MediumCVSS 6.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a medium-severity tampering vulnerability in Microsoft Edge for Android. A successful attack could cause limited confidentiality, integrity, and availability impact, but the CVSS data says user interaction is required. The provided sources do not show known active exploitation.

Executive priority

Treat as a routine but necessary mobile browser patching item. It does not currently justify emergency response based on the provided evidence, but unmanaged Android devices could leave business users exposed.

Technical view

CVE-2023-36888 is a Microsoft Edge for Android tampering issue mapped to CWE-20. The CVSS 3.1 vector indicates network attack path, low complexity, no privileges, required user interaction, unchanged scope, and low confidentiality, integrity, and availability impact. Microsoft lists official remediation and confirmed report confidence.

Likely exposure

Exposure is limited to environments with Microsoft Edge for Android, specifically the affected product/version data provided by Microsoft/CVE. Confirm Android fleet inventory through MDM, endpoint management, or app-store telemetry.

Exploitation context

The bundle marks KEV as false and CVSS exploit code maturity as unproven. No cited source in the bundle supports active exploitation. User interaction is required, reducing urgency compared with unauthenticated no-click mobile issues.

Researcher notes

The public bundle is sparse: it names tampering, CWE-20, affected Microsoft Edge for Android, and CVSS details, but does not describe root cause, attack scenario, or fixed version. Avoid assumptions beyond Microsoft guidance.

Mitigation direction

  • Review Microsoft’s advisory for the official Edge for Android remediation.
  • Update Microsoft Edge for Android through managed app stores or MDM.
  • Prioritize managed Android devices used for sensitive business access.
  • Follow vendor guidance if updates are delayed or unavailable.

Validation and detection

  • Inventory Android devices with Microsoft Edge installed.
  • Confirm deployed Edge for Android versions against Microsoft’s advisory.
  • Check MDM or app-store reporting for successful update rollout.
  • Track exceptions for unmanaged or update-blocked devices.
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 · low confidence lookup

CWE-20: 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
cve · low confidence lookup

CVE-2023-36888 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
Medium
CVSS
6.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L/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
2Source 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
6.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L/E:U/RL:O/RC:C2.83.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.3Medium
CVSS 3.1 vector shape for CVE-2023-36888Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftMicrosoft Edge for Android1.0.0Listed
Weakness

CWE details

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

CWE-20 · source CWE mapping

Improper Input Validation

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