# CVE-2015-2426: Microsoft Windows Adobe Type Manager Library Remote Code Execution

> Remote attackers can execute arbitrary code via a crafted OpenType font due to a buffer underflow in the Windows Adobe Type Manager Library.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 28 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Jul 2015
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-7w6v-23gr-722w

## What is CVE-2015-2426?

CVE-2015-2426 is a high-severity memory corruption vulnerability in Microsoft Windows 10, published on 20 Jul 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer underflow in atmfd.dll in the Windows Adobe Type Manager Library in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1 allows remote attackers to execute arbitrary code via a crafted OpenType font, aka "OpenType Font Driver Vulnerability."

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), CWE-124 (Buffer Underwrite)

## Which versions are affected by CVE-2015-2426?

It affects 9 products.


Products: Microsoft Windows 10, Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 8.1, Microsoft Windows Rt, Microsoft Windows Rt 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Vista.

## How do I fix CVE-2015-2426?

No fix has been published for CVE-2015-2426 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 18 Apr 2022.

## Is CVE-2015-2426 being exploited?

Yes. Attackers have exploited CVE-2015-2426 in the wild since at least 28 Mar 2022.

Public exploit code:

- MS15-078 Microsoft Windows Font Driver Buffer Overflow (metasploit)
- Microsoft Windows - Font Driver Buffer Overflow (MS15-078) (Metasploit) (exploitdb)

## Other vulnerabilities in Microsoft Windows 10

- [CVE-2015-1769](https://insights.sbomify.com/CVE-2015-1769/): Microsoft Windows Mount Manager Privilege Escalation (medium 6.6, exploited in the wild)
- [CVE-2020-1467](https://insights.sbomify.com/CVE-2020-1467/): Windows Hard Link Elevation of Privilege Vulnerability (critical 10.0)
- [CVE-2021-26424](https://insights.sbomify.com/CVE-2021-26424/): Windows TCP/IP Remote Code Execution Vulnerability (critical 9.9)
- [CVE-2021-28476](https://insights.sbomify.com/CVE-2021-28476/): Windows Hyper-V Remote Code Execution Vulnerability (critical 9.9)
- [CVE-2021-26867](https://insights.sbomify.com/CVE-2021-26867/): Windows Hyper-V Remote Code Execution Vulnerability (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2426 and fix it if it is affected.

What it is: CVE-2015-2426 is a high-severity memory corruption vulnerability in Microsoft Windows 10, published on 20 Jul 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2015-2426 in the wild since at least 28 Mar 2022.

Affected product: Microsoft Windows 10. 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-2015-2426/ (Markdown: https://insights.sbomify.com/CVE-2015-2426/index.md)
```

## Sources

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

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