HIGH 7.4

CVE-2026-57991: Microsoft Edge Link-Following Information Disclosure Vulnerability

Microsoft Edge (Chromium-based) contains a flaw in how it resolves symbolic links and shortcuts before accessing files. An attacker can craft a malicious link that, when clicked by a user, causes Edge to follow the link to an unintended location and disclose sensitive information over the network. The vulnerability requires user interaction (clicking the link) but does not require authentication and can affect systems across a network.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.4 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
Weaknesses (CWE)
CWE-59
Affected products
1 configuration(s)
Published / Modified
2026-07-03 / 2026-07-07

NVD description (verbatim)

Improper link resolution before file access ('link following') in Microsoft Edge (Chromium-based) allows an unauthorized attacker to disclose information over a network.

1 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-57991 is a link-following vulnerability (CWE-59: Improper Link Resolution Before File Access) in Microsoft Edge's Chromium engine. The flaw allows an attacker to craft a specially designed symbolic link or shortcut that bypasses proper validation before file access. When a user clicks or interacts with the malicious link within Edge, the browser resolves it to an unintended target, potentially exposing sensitive file contents to the attacker over the network. The vulnerability has a CVSS 3.1 score of 7.4 (HIGH) with a network-based attack vector, low attack complexity, no privileges required, and a user interaction requirement. The impact is limited to confidentiality; integrity and availability are not affected.

Business impact

This vulnerability poses a moderate but real risk to organizations where users may encounter untrusted links or content. Potential business impacts include: data exfiltration of sensitive files accessible by the user's Edge browser context; competitive or operational intelligence leakage if employees access confidential documents through Edge; and reputational harm if customer or partner data is disclosed. The requirement for user interaction limits blast radius compared to remote code execution flaws, but phishing or social engineering campaigns could reliably exploit this in targeted scenarios.

Affected systems

Microsoft Edge (Chromium-based) is affected. The vulnerability applies across Windows, macOS, Linux, and other platforms where Edge is deployed. Users and organizations operating any current or near-current version of Chromium-based Edge prior to a patch are at risk. Verify the specific affected version ranges against Microsoft's official security advisory.

Exploitability

Exploitability is moderate. An attacker must craft a malicious link or host it on a web page or send it via email/messaging. The target user must click or otherwise interact with the link, making this suitable for phishing or social engineering campaigns rather than unauthenticated worm-style propagation. No authentication is required, and the attack is network-accessible. Once clicked, the vulnerability is reliably triggered on vulnerable versions. The requirement for user interaction prevents automated, mass-scale exploitation but does not significantly reduce risk in targeted or campaign-based attack scenarios.

Remediation

Apply the latest security patch for Microsoft Edge (Chromium-based) released by Microsoft to address CVE-2026-57991. Verify the specific patched version through Microsoft's official security advisory. In the interim, users can reduce risk by: avoiding clicking suspicious links or links from untrusted sources; disabling or restricting link handling in Edge if organizational policy permits; and educating users on link-following attacks and phishing tactics.

Patch guidance

Monitor Microsoft Edge's official security advisories and release notes for the patched version addressing CVE-2026-57991. Deploy patches through your organization's standard update management process (Windows Update, enterprise deployment tools, or manual updates depending on your deployment model). Test patches in a non-production environment if feasible before full rollout. Verify remediation by confirming all user and system instances of Edge are running the patched or newer build version.

Detection guidance

Monitor network traffic for exfiltration of sensitive files or data transfers initiated by Edge processes to unexpected destinations. Review browser logs and file access audits for unusual file access patterns triggered by link interactions. Endpoint Detection and Response (EDR) tools can flag suspicious file access or symbolic link resolution by edge.exe or the Edge process. Web proxies and firewalls may help block malicious link hosting domains. User reporting of unexpected file dialogs or access prompts when clicking links is also a detection signal.

Why prioritize this

This vulnerability warrants high priority due to its HIGH CVSS score, network-accessible attack vector, and broad applicability across Edge users. While user interaction is required, the low attack complexity and the prevalence of phishing campaigns make it a realistic and immediate threat in most threat models. Organizations with strict user access controls and strong phishing filters can lower the relative priority, but enterprises cannot afford to deprioritize it entirely.

Risk score, explained

The CVSS 3.1 score of 7.4 (HIGH) reflects the combination of network-based attack surface, low complexity, no authentication requirement, and confidentiality impact. The user interaction requirement and lack of integrity or availability impact prevent a critical rating. In a real-world context, risk is elevated by the human element (phishing success rates) and the potential sensitivity of files accessible in user contexts.

Frequently asked questions

Does this vulnerability allow remote code execution?

No. CVE-2026-57991 is limited to information disclosure (confidentiality impact only). An attacker can cause Edge to access and potentially exfiltrate sensitive files, but cannot execute arbitrary code, modify files, or crash the browser. This limits but does not eliminate the risk.

Do I need to do anything other than apply the patch?

Patching is the primary remediation. No configuration changes or workarounds are documented as necessary once a patched version is deployed. However, user awareness training on phishing and suspicious links remains a strong complementary defense.

Is this vulnerability actively exploited in the wild?

As of the publication date (July 3, 2026), this vulnerability is not listed on CISA's Known Exploited Vulnerabilities (KEV) catalog, indicating no confirmed active exploitation in the wild. However, the lack of a KEV entry does not guarantee future safety; monitor threat intelligence feeds for any changes.

Which Edge versions are affected?

Verify the specific affected version ranges through Microsoft's official security advisory for CVE-2026-57991. This intelligence page does not specify version numbers; always refer to the vendor advisory for definitive impact assessment.

This analysis is provided for informational and educational purposes. SEC.co does not guarantee the accuracy, completeness, or timeliness of vulnerability details. Always verify information against official vendor advisories (Microsoft Security Response Center) and maintain independent security posture assessment. Patch version numbers and specific affected product versions must be confirmed against the vendor advisory before deployment. Security risk is contextual; assess impact based on your environment, user behavior, and data sensitivity. This page does not constitute legal, compliance, or professional security advice. Source: NVD (public-domain), retrieved 2026-08-12. Analysis generated by SEC.co (claude-haiku-4-5).