Skip to navigation

Threat reportVulnerabilityTL-2026-1505

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

highACTIVE

CVE-2026-58525 is a CVSS 8.2 improper-access-control flaw (CWE-284) in Microsoft Edge (Chromium-based) prior to version 150.0.4078.50 that lets a remote, unauthenticated attacker bypass a browser security restriction if a user is enticed to open a specially crafted web page. No public PoC and no active exploitation are reported; Microsoft rates it 'Important' with Exploit Code Maturity Unknown (E:U), and CISA SSVC rates exploitation as 'none' and technical impact as 'partial'.

Key facts

IdentifiersTL-2026-1505, CVE-2026-58525, CVE-2026-58523
SeverityHIGH
CVSS8.2 (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)
EPSSCVE-2026-58523: 0.8% (57.7th percentile); CVE-2026-58525: 0.5% (41.9th percentile)
Affected productsMicrosoft Microsoft Edge (Chromium-based)
Weaknesses (CWE)CWE-284
MITRE ATT&CK techniquesT1005 Data from Local System, T1189 Drive-by Compromise, T1204 User Execution, T1211 Exploitation for Stealth, T1217 Browser Information Discovery, T1539 Steal Web Session Cookie, T1548 Abuse Elevation Control Mechanism, T1566 Phishing, T1583 Acquire Infrastructure, T1594 Search Victim-Owned Websites, T1608 Stage Capabilities, T1685 Disable or Modify Tools
MotivationUNKNOWN
Target sectorsgovernment administration, enterprise, finance, health, technology, all-browser-users
Target regionshong kong, Global
Detection rules9 (1 shown free)
Sources9 cited sources

Detection coverage

As of 2026-07-08, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1505 across Splunk SPL, Microsoft KQL and Sigma, covering 21 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Edge Launch Immediately Following Suspicious Attachment Open (CVE-2026-58525 Enticement)

Detects msedge.exe spawned within minutes of Outlook/Teams/Explorer writing a new attachment to disk and opening a file:// or local-content URL, matching the documented CVE-2026-58525 enticement-to-crafted-page attack path (T1566.001 -> T1608.001 -> T1204.001).

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1566.001, T1608.001, T1204.001
  • Data sources: sysmon, windows_security, microsoft_defender_for_endpoint
  • Severity: high
  • Confidence: medium

Splunk SPL

index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1 Image="*\\msedge.exe" (CommandLine="*file:///*" OR CommandLine="*--new-window*")
| eval parent_proc=lower(ParentImage)
| where match(parent_proc, "outlook\.exe$") OR match(parent_proc, "teams\.exe$") OR match(parent_proc, "explorer\.exe$")
| eval edge_launch_time=_time
| join type=left ParentProcessId [ search index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=11 TargetFilename="*.htm*" OR TargetFilename="*.lnk*" OR TargetFilename="*Invoice*" | rename ProcessId as ParentProcessId | eval attach_write_time=_time | table ParentProcessId attach_write_time TargetFilename ]
| where isnotnull(attach_write_time) AND (edge_launch_time - attach_write_time) <= 300
| table _time ComputerName User Image CommandLine ParentImage TargetFilename edge_launch_time attach_write_time
| sort -_time

Microsoft KQL

let PatchedBuild = "150.0.4078.50";
DeviceProcessEvents
| where Timestamp > ago(24h)
| where FileName =~ "msedge.exe"
| where ProcessCommandLine has_any ("file:///", "--new-window")
| where InitiatingProcessFileName in~ ("OUTLOOK.EXE", "Teams.exe", "explorer.exe")
| join kind=leftouter (
    DeviceFileEvents
    | where Timestamp > ago(24h)
    | where FileName has_any (".htm", ".lnk", "Invoice")
    | project AttachTime = Timestamp, InitiatingProcessId, AttachFileName = FileName
) on InitiatingProcessId
| where isnotempty(AttachFileName) and (Timestamp - AttachTime) between (0min .. 5min)
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, AttachFileName

Sigma

title: Edge Launch Immediately Following Suspicious Attachment Open (CVE-2026-58525 Enticement Pattern)
id: 8f2b0a1e-6f2d-4a55-9d1f-1a2b3c4d5e6f
status: experimental
description: Detects Microsoft Edge (msedge.exe) launched with a file:// or non-standard local-content URL shortly after a mail/IM client wrote an attachment, consistent with the CVE-2026-58525 enticement-to-crafted-page pattern.
references:
    - https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-58525
    - https://www.govcert.gov.hk/en/alerts_detail.php?id=1956
author: Threadlinqs Team
date: 2026-07-19
tags:
    - attack.initial-access
    - attack.execution
    - attack.t1566.001
    - attack.t1608.001
    - attack.t1204.001
    - cve.2026.58525
logsource:
    product: windows
    category: process_creation
detection:
    selection_edge:
        Image|endswith: '\msedge.exe'
        CommandLine|contains:
            - 'file:///'
            - '--new-window'
    selection_recent_attachment:
        ParentImage|endswith:
            - '\OUTLOOK.EXE'
            - '\Teams.exe'
            - '\explorer.exe'
    condition: selection_edge and selection_recent_attachment
falsepositives:
    - Legitimate users opening local HTML reports or exported HTML email attachments in Edge for routine work
    - IT-generated HTML dashboards distributed via email and opened by end users
level: medium

Known false positives:

  • Legitimate users opening local HTML reports or exported HTML email attachments in Edge for routine work
  • IT-generated HTML dashboards distributed via email and opened by end users

Tuning notes: Narrow the 5-minute join window if noisy; add an allow-list of internal HTML report senders/domains, and exclude known SaaS webmail HTML export workflows specific to the environment.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Spearphishing Attachment Followed by Edge Local-File Navigation (T1566.001 -> T1204.001) · unlock with TL Creds
  • Post-Bypass Browser Profile Enumeration and Local-System Staging (T1217 / T1005) · unlock with TL Creds
  • Defense-Evasion Indicators Correlated with Unpatched Edge Security-Feature-Bypass Exposure · unlock with TL Creds
  • Reconnaissance/Infrastructure-Staging Precursor to Edge-Targeted Phishing Campaign · unlock with TL Creds
  • Spearphishing Link Click-Through to Edge with External URL Command Line (T1566.002) · unlock with TL Creds
  • Elevation/Abuse-Control Attempt Immediately Following Suspected Boundary-Bypass Session (C2/Lateral Follow-On) · unlock with TL Creds
  • Sub-Patch Edge Version Loading Untrusted External URL (CVE-2026-58525 Exposure Window) · unlock with TL Creds
  • Rapid Edge Cookie/LocalStorage Read Following Untrusted Navigation (Boundary-Bypass Pattern) · unlock with TL Creds

Indicators of compromise

As of 2026-07-08, Threadlinqs Intelligence tracks 21 indicators of compromise for TL-2026-1505.

21 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

CVE-2026-58525 was disclosed by Microsoft on July 8, 2026 as part of the July 2026 Patch Tuesday release, which the Zero Day Initiative's monthly review characterized as an unusually large cycle — ZDI's published review states the month shipped 621 CVEs in total, of which a large cluster (reported elsewhere as roughly 480) were Chromium-related, calling it a 'Mother of All Releases.' The flaw is classified as CWE-284 (Improper Access Control) in the Chromium-based build of Microsoft Edge and carries a CVSS 3.1 base score of 8.2 (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, temporal ~7.1); NVD has not yet published a CVSS v4.0 assessment for this CVE. The attack path requires no authentication and no special privileges, but does require user interaction: an attacker hosts a specially crafted web page and must entice a target to open it, typically via a phishing email, instant-message lure, or a malicious attachment/link sent through email — this enticement-via-attachment vector is explicitly called out in Microsoft's own description of the attack path. Once the page is loaded, the improper access-control logic allows the attacker to circumvent an expected browser security restriction, changing the scope of impact (S:C) and yielding high confidentiality impact (C:H) with limited integrity impact (I:L) and no availability impact (A:N) — consistent with a security-boundary bypass that exposes browser-protected data or state (e.g., session/origin-isolation data) rather than granting code execution or denial of service. Microsoft's own exploitability metrics record E:U (exploit code maturity unknown), RL:O (official fix available), and RC:C (report confidence confirmed); CISA's SSVC scoring for the CVE records exploitation status as 'none,' automatable as 'no,' and technical impact as 'partial.' Neither Microsoft, GovCERT.HK, nor the Zero Day Initiative's July 2026 review report any public proof-of-concept or in-the-wild exploitation as of publication, and the CVE is absent from the CISA Known Exploited Vulnerabilities (KEV) catalog as of 2026-07-19. Microsoft fixed the issue in Edge Stable 150.0.4078.50 (released July 8, 2026 across Windows, macOS, and other supported channels), and GovCERT.HK issued Security Alert A26-07-16 the following day urging Hong Kong organizations to update. The July 2026 Patch Tuesday cycle also shipped two closely related Edge (Chromium-based) Security Feature Bypass vulnerabilities — CVE-2026-57983 (CVSS 8.7) and CVE-2026-58295 (CVSS 8.3) — plus a lower-severity companion, CVE-2026-58523, affecting Microsoft Edge for Android (CVSS 6.5), indicating a cluster of access-control hardening fixes shipped to the Edge/Chromium codebase in the same release rather than an isolated one-off defect. NVD's record and third-party trackers (thewindowsupdate.com, datacomm.com, cve.threatint) mirror MSRC's advisory text verbatim, with no independent technical write-up, exploit chain analysis, or PoC code published by any tracked source, reflecting the genuinely thin public documentation typical of this CVE class before independent researchers reverse-engineer the patch diff.

MITRE ATT&CK techniques by tactic:

Collection

T1005 Data from Local System

Initial Access

T1189 Drive-by Compromise; T1566 Phishing

Execution

T1204 User Execution

Defense Evasion

T1211 Exploitation for Stealth

Discovery

T1217 Browser Information Discovery

Credential Access

T1539 Steal Web Session Cookie

privilege-escalation

T1548 Abuse Elevation Control Mechanism

Resource Development

T1583 Acquire Infrastructure; T1608 Stage Capabilities

Reconnaissance

T1594 Search Victim-Owned Websites

defense-impairment

T1685 Disable or Modify Tools

Remediation

Patches

  • Microsoft Edge (Chromium-based) Stable 150.0.4078.50 (released 2026-07-08) resolves CVE-2026-58525.

Immediate actions

  • Update Microsoft Edge (Chromium-based) to version 150.0.4078.50 or later on all Windows, macOS, and managed endpoints.
  • Push the Edge security update via enterprise patch/update management (Microsoft Intune, WSUS, Configuration Manager, or the Edge auto-update channel) rather than waiting for opportunistic user-driven updates.
  • Verify current Edge version fleet-wide via managed browser telemetry to confirm no endpoints remain below 150.0.4078.50.

Workarounds

  • No official workaround is published; updating to the fixed build is the only remediation documented by Microsoft/GovCERT.HK.

Longer-term hardening

  • Enforce Edge auto-update policies and block user ability to defer or disable browser updates on managed devices.
  • Maintain browser patch-compliance monitoring as part of standard vulnerability management given the recurring cadence of Edge/Chromium Security Feature Bypass CVEs (this release alone shipped three: CVE-2026-58525, CVE-2026-57983, CVE-2026-58295).
  • Layer web/email gateway filtering and user security-awareness training against enticement-based lures, since exploitation of this CVE class depends on convincing a user to open a crafted link or attachment.
  • Continue monitoring CISA KEV and vendor advisories for this CVE cluster; SSVC currently rates exploitation 'none' and automatable 'no,' but that can change if a researcher publishes a patch-diff-derived PoC.

Affected and fixed versions

  • Microsoft — Microsoft Edge (Chromium-based)
    Vulnerable versions: < 150.0.4078.50
    Fixed in: 150.0.4078.50

Timeline

  • Third-party trackers (thewindowsupdate.com, DataComm Networks, THREATINT) republish the MSRC advisory text for CVE-2026-58525 the same day, with no added technical detail.
  • NVD publishes its own record for CVE-2026-58525 mirroring the MSRC CVSS 3.1 vector and CWE-284 classification; CVSS v4.0 not yet assessed.
  • Microsoft Edge (Chromium-based) Stable version 150.0.4078.50, which fixes CVE-2026-58525, released for Windows and macOS.
  • CVE-2026-58525 published by Microsoft via the MSRC Security Update Guide as part of July 2026 Patch Tuesday, rated CVSS 8.2 / Important.
  • GovCERT.HK issues Security Alert A26-07-16 covering the Microsoft Edge vulnerability and recommending users update to the patched version.
  • NVD record for CVE-2026-58525 last-modified; CISA SSVC scoring recorded for the CVE as exploitation 'none,' automatable 'no,' technical impact 'partial.'
  • Zero Day Initiative publishes its July 2026 Security Update Review, listing CVE-2026-58525 among the month's 621 total CVEs (with roughly 480 characterized as Chromium-related) and describing the cycle as a 'Mother of All Releases,' with no known public exploitation reported for this CVE.
  • TL-Intel Harness HUNT phase selects CVE-2026-58525 for deep-dive research after it cleared the CVSS >= 7.0 network-attack-vector selection threshold from the GovCERT.HK feed.
  • CVE-2026-58525 confirmed absent from the CISA Known Exploited Vulnerabilities (KEV) catalog as of this date.

Sources cited

Previous and next in vulnerability

Further reading

Drafted by the Threadlinqs research pipeline from 9 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats