LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26188: Microsoft Edge (Chromium-based) Spoofing Vulnerability

Microsoft Edge (Chromium-based) Spoofing Vulnerability

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a medium-severity spoofing flaw in Microsoft Edge for Android. A malicious remote party could misrepresent information to a user and influence a decision, but user interaction is required. The supplied scoring indicates limited integrity impact, with no stated confidentiality or availability impact.

Executive priority

Address through routine mobile browser patching, with prompt attention where the listed version is deployed. Urgency is moderated by required user interaction, limited stated impact, and no evidence of active exploitation.

Technical view

CVE-2024-26188 is classified as CWE-357, involving insufficiently trustworthy UI presentation. It is remotely reachable, requires low attack complexity, no privileges, and user interaction. The supplied affected data identifies Microsoft Edge for Android version 1.0.0 only. The source bundle provides no further technical mechanism.

Likely exposure

Exposure is indicated only for organizations or users running Microsoft Edge for Android version 1.0.0. The supplied evidence does not establish whether later versions are affected, nor describe required configuration or browsing conditions.

Exploitation context

The CVSS exploit-maturity value is unproven, and the CVE is not identified as CISA KEV. No supplied source establishes active exploitation or public exploit availability. Successful abuse requires user interaction.

Researcher notes

The supplied record is unusually sparse: it names spoofing and CWE-357 but provides no affected UI component, attack scenario, or corrected version. Treat the version scope literally and avoid extrapolating to other Edge platforms or releases without additional Microsoft evidence.

Mitigation direction

  • Update Microsoft Edge for Android according to Microsoft’s CVE advisory.
  • Prioritize managed Android devices confirmed to run the listed affected version.
  • Review Microsoft guidance for any additional mitigations or corrected-version details.

Validation and detection

  • Inventory Microsoft Edge versions installed across managed Android devices.
  • Confirm affected installations no longer report version 1.0.0 after updating.
  • Review the Microsoft advisory for corrected-version and deployment verification information.
  • Recheck mobile application management reports for devices that missed remediation.
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-357: 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-2024-26188 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
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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
2ADP 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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N/E:U/RL:O/RC:C2.81.4microsoft

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2024-26188Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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-357 · source CWE mapping

Insufficient UI Warning of Dangerous Operations

Insufficient UI Warning of Dangerous Operations represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.