# CVE-2024-26167: Microsoft Edge for Android Spoofing Vulnerability


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Mar 2024
- **Updated:** 3 May 2025
- **Also known as:** GHSA-4p27-6j8h-cjhw

## What is CVE-2024-26167?

CVE-2024-26167 is a medium-severity vulnerability in Microsoft Edge, published on 7 Mar 2024. 

### Official description

Microsoft Edge for Android Spoofing Vulnerability

Weakness: CWE-1021 (Improper Restriction of Rendered UI Layers or Frames)

## Which versions are affected by CVE-2024-26167?

It affects 1 product.


Products: Microsoft Edge.

## How do I fix CVE-2024-26167?

No fix has been published for CVE-2024-26167 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-26167 being exploited?

There is no known exploitation of CVE-2024-26167 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Edge

- [CVE-2021-26411](https://insights.sbomify.com/CVE-2021-26411/): Microsoft Internet Explorer Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2016-7200](https://insights.sbomify.com/CVE-2016-7200/): Microsoft Edge Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2016-7201](https://insights.sbomify.com/CVE-2016-7201/): Microsoft Edge Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2017-0037](https://insights.sbomify.com/CVE-2017-0037/): Microsoft Edge and Internet Explorer Type Confusion (high 8.1, exploited in the wild)
- [CVE-2016-3351](https://insights.sbomify.com/CVE-2016-3351/): Microsoft Internet Explorer and Edge Information Disclosure (medium 6.5, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-26167 and fix it if it is affected.

What it is: CVE-2024-26167 is a medium-severity vulnerability in Microsoft Edge, published on 7 Mar 2024. 
Exploitation: There is no known exploitation of CVE-2024-26167 in the wild and no public exploit code.

Affected product: Microsoft Edge. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-26167/ (Markdown: https://insights.sbomify.com/CVE-2024-26167/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-26167
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-26167
- OSV: https://osv.dev/vulnerability/CVE-2024-26167

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-26167/
Summaries are generated and may contain mistakes; the official description above is the record.