Skip to main content

Microsoft Edge CVE-2026-88078

| EUVDEUVD-2026-112940 MEDIUM
Improper Verification of Cryptographic Signature (CWE-347)
2026-10-29 microsoft GHSA-hgfw-55vg-gxmm
4.3
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Lure victim Edge user to malicious content
  2. Exploit
    Serve payload with improperly verified signature
  3. Execution
    Edge accepts forged/invalid signature as valid
  4. Impact
    Spoof trusted content or identity to user

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Signature verification
Exploitation Conditions

Exploitation requires an Edge user to interact with attacker-supplied content (UI:R) - for example visiting or engaging with a malicious page - allowing the attacker to exploit improper cryptographic-signature verification to spoof trusted content over the network without authentication (PR:N). Limiting factors: the required user interaction, the confined impact (integrity-only spoofing, no code execution or data disclosure), and the availability of a vendor patch; affected builds are Microsoft Edge (Chromium-based) 1.0.0.0 through versions below 156.0.4314.42, so updating to 156.0.4314.42 or later removes exposure. The description does not specify any particular feature or non-default configuration as a precondition.

Impact

This is a moderate-severity spoofing issue (CVSS 4.3) whose real-world priority is limited despite the network attack vector. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) shows an unauthenticated network-reachable flaw, but impact is confined to a low integrity hit (spoofing) with no confidentiality or availability loss, and exploitation requires user interaction (UI:R). The temporal metrics reinforce a low urgency posture: E:U (exploit unproven), RL:O (official fix available), and RC:C (confirmed). No CISA KEV listing and no POC are present in the input, and no EPSS score was provided, so exploitation probability cannot be quantified from the data. The vuln.today decision label is 'this_month' - meaningfully below act_now/emergency - which is consistent with the low-impact, no-known-exploit signal set. The one amplifying factor is prevalence: Microsoft Edge is extremely widely deployed, so even a low-impact flaw has a large exposed population. Net assessment: a legitimate issue to patch on a routine monthly cadence, not an emergency; the signals are internally consistent rather than conflicting, with the main data gap being the absence of EPSS.

Exploit ScenarioDerived

An attacker lures a victim Edge user to attacker-controlled web content; because Edge improperly verifies a cryptographic signature (CWE-347), the attacker presents content that appears to carry a valid/trusted signature, spoofing trusted identity or UI to the user. No public exploit was identified at time of analysis (CVSS E:U), and success depends on user interaction (UI:R), typically visiting or interacting with the malicious content.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 29, 2026

Spoofing of trusted content in Microsoft Edge (Chromium-based) builds earlier than 156.0.4314.42 stems from improper verification of cryptographic signatures (CWE-347), letting an unauthorized remote attacker present content as though it originated from a trusted source. The assessed vector is CVSS 4.3 (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N): no authentication is required, but the victim Edge user must interact with attacker-supplied content, and the impact is confined to a low-integrity spoofing effect with no confidentiality or availability loss. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; Microsoft has released a vendor patch, and the attacker value is rated E:U with RL:O, so the practical priority is a routine monthly update rather than emergency response.

RemediationAI

Vendor-released patch: Microsoft Edge 156.0.4314.42 (or later). Update every Edge (Chromium-based) installation, including stable, extended-stable, beta, dev and canary channels and any pinned/frozen builds used in gold images or VDI, to 156.0.4314.42 or higher; consumer installs normally pick this up automatically through the browser updater, while managed fleets should verify the target version in the Edge update policy and confirm the reported browser version after the update cycle. Verify remediation by checking the Edge version string on endpoints and by confirming the deployment rings have actually advanced past 156.0.4314.42, since deferral policies are the main reason an endpoint would remain on an affected build. Advisory and detection guidance are at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-88078. The available sources describe updating to 156.0.4314.42 or later as what removes exposure; no separate workaround or configuration-level mitigation is documented in the supplied data.

Affected VersionsENISA

Microsoft Edge (Chromium-based) 1.0.0.0 <156.0.4314.42

Affected Packages

euvd microsoft_edge_chromium_based fix: 156.0.4314.42

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a cryptographic signature verification weakness (CWE-347, Improper Verification of Cryptographic Signature) in Microsoft Edge's Chromium-based rendering/platform stack, meaning Edge accepts or mis-validates a signature-backed artifact as trustworthy when it should not. The affected CPE is cpe:2.3:a:microsoft:microsoft_edge_(chromium-based):*:*:*:*:*:*:*:*, i.e. the general Edge product line below build 156.0.4314.42; the specific component, signed object type, and validation path are not described in the available sources, and the trigger is not described either. Third-party tagging associates the CVE with JWT-related signature handling, which would point at token or assertion verification in the browser, but that association is a tag mapping only and is unverified against the vendor text; no non-default configuration or particular Edge feature is stated as a precondition. Because the impact is integrity-only (I:L) with no code execution or data disclosure and requires user interaction (UI:R), the weakness is best understood as a trust/authenticity bypass surface rather than a memory-safety or sandbox-escape primitive.

Know when Jwt Attack gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (microsoft) PRIMARY 4.3 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
vuln.today AI 4.3 MEDIUM

Network-reachable and unauthenticated (AV:N/PR:N) but needs the user to interact with attacker content (UI:R); spoofing yields only limited integrity impact (I:L) with no confidentiality or availability loss.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

DescriptionCVE.org

Improper verification of cryptographic signature in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform spoofing over a network.

Threat Intelligence Overview

EPSS Score
0.3%
Top 77% exploitable
Prevalence
Ubiquitous
Microsoft Edge is bundled as the default browser across Windows endpoints
Vendor Status
Publicly Disclosed:No
Exploited:No
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

22
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +22
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2013-3900 MEDIUM
5.5 Dec 11

Why is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update

CVE-2026-48558 CRITICAL POC
9.5 Jun 12

Authentication bypass in SimpleHelp 5.5.15 and prior (plus 6.0 pre-release builds) allows remote unauthenticated attacke

CVE-2026-5430 CRITICAL POC
10.0 Aug 06

Authentication bypass in WSO2 API Manager and related components (Universal Gateway, Traffic Manager, API Control Plane,

CVE-2025-59718 CRITICAL
9.8 Dec 09

Authentication bypass in Fortinet FortiOS, FortiProxy, and FortiSwitchManager allows unauthenticated remote attackers to

CVE-2025-25291 CRITICAL POC
9.3 Mar 12

ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS

CVE-2026-47304 CRITICAL POC
9.8 Jul 14

Security feature bypass in Microsoft .NET (shipped via Visual Studio 2022 17.12/17.14 and Visual Studio 2026 18.7) lets

CVE-2025-25292 CRITICAL POC
9.3 Mar 12

ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS

CVE-2022-25898 CRITICAL POC
9.8 Jul 01

The package jsrsasign before 10.5.25 are vulnerable to Improper Verification of Cryptographic Signature when JWS or JWT

CVE-2026-107722 CRITICAL POC
9.8 Oct 08

Authentication and authorization bypass in fast-jwt 6.2.0 through 6.2.4 (npm, NearForm) lets a remote, unauthenticated a

CVE-2024-42004 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in Microsoft Teams (work or school) 24046.2813.2770.1094 for macOS. Rated criti

CVE-2024-41145 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in the WebView.app helper app of Microsoft Teams (work or school) 24046.2813.27

CVE-2024-41138 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in the com.microsoft.teams2.modulehost.app helper app of Microsoft Teams (work

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy