Cyber Resilience

CVE-2026-58595

Microsoft Bing Search ≤ 33.4.440529002

Published
14 July 2026
Modified
24 July 2026
Patch / advisory
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
EPSS Score 0.0046 38th percentile
Risk Priority 60 floored blend · peak EPSS

Summary

CVE-2026-58595 is a high-severity Improper Restriction of Rendered UI Layers or Frames (CWE-1021) vulnerability in Microsoft Bing Search. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Drive-by Compromise (T1189); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Improper restriction of rendered ui layers or frames in Microsoft Bing App for IOS allows an unauthorized attacker to perform spoofing over a network.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
T1056 Input Capture Collection
Adversaries may use methods of capturing user input to obtain credentials or collect information.
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-26167Same vendor: Microsoft
CVE-2024-30041Same product: Microsoft Bing Search
CVE-2024-29981Same vendor: Microsoft
CVE-2025-6557Same vendor: Microsoft
CVE-2025-14373Same vendor: Microsoft
CVE-2026-10733Shared CWE-1021
CVE-2026-38979Shared CWE-1021
CVE-2025-63522Shared CWE-1021
CVE-2024-2613Shared CWE-1021
CVE-2023-47774Shared CWE-1021

Affected Assets

microsoft
bing search
≤ 33.4.440529002

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require implementing frame-ancestors / X-Frame-Options controls that prevent this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect missing frame protections, but does not itself implement the control.

degrades

Web filtering can block or sandbox untrusted frames, but does not enforce application-level frame-busting or CSP.

prevents

Application security requirements can mandate frame-ancestors / X-Frame-Options, directly addressing UI redressing risks.

prevents

Secure architecture principles include isolation of UI layers and proper use of browser security controls.

prevents

Secure coding practices directly require implementation of frame-busting headers or CSP frame-ancestors directives.

References