Is there a public exploit for CVE-2026-58289?

Yes. An exploit for CVE-2026-58289 is archived and downloadable from Exploit-DB.

How severe is CVE-2026-58289?

CVE-2026-58289 scores CVSS 9 (v3.1), rated critical. EPSS puts the chance of exploitation in the next 30 days at 1.99%.

What does CVE-2026-58289 affect?

CVE-2026-58289 affects Microsoft Microsoft Edge (Chromium-based).

9.0 Critical

Access of resource using incompatible type ('type confusion') in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute…

CVE-2026-58289

Access of resource using incompatible type ('type confusion') in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.

A public exploit is available

Exploit-DB

Exploit-DBMicrosoft Edge 150.0.4078.48 - RCE

Signals come from Exploit-DB, Metasploit, Nuclei and published proof-of-concept repositories. Their absence means nothing was found, not that nothing exists.

Assessment

CVSS: 9 (v3.1)
Severity: Critical
EPSS: 1.99% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Exploit-DB
Published: 3 July 2026
Last updated: 1 November 2026
Affected: Microsoft · Microsoft Edge (Chromium-based)
Assigner: microsoft

CVSS vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C

At the source

EUVD (ENISA)

References

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-58289

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 4 + 1? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-58289