Is AutoMapper 16.1 vulnerable?
NuGet · 2 releases from 16.1.0 to 16.1.1 · latest AutoMapper is 17.0.0 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. AutoMapper 16.1.1, the last 16.1 release, is affected by 2 known security advisories (2 high), including CVE-2026-128082, CVE-2026-128081. 1 more affects earlier 16.1.x releases. Upgrade to 16.3.0 or later to fix all of them.
dotnet add package AutoMapper --version 16.3.0Is your project on an affected AutoMapper?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting AutoMapper 16.1.1
AutoMapper: Uncontrolled Recursion with Constructor Parameters
- Affected
- >=16.0.0 <16.3.0 · <15.1.4
- Fixed in
- 15.1.4, 16.3.0
AutoMapper: Denial of Service via uncontrolled recursion that bypasses MaxDepth
- Affected
- >=16.0.0 <16.3.0 · <15.1.4
- Fixed in
- 15.1.4, 16.3.0
Fixed within 16.1.x, affecting earlier releases
AutoMapper Vulnerable to Denial of Service (DoS) via Uncontrolled Recursion
- Affected
- >=16.0.0 <16.1.1 · <15.1.1
- Fixed in
- 15.1.1, 16.1.1
Every AutoMapper 16.1.x release
Affected: 16.1.0 to 16.1.1. Latest AutoMapper: 17.0.0.
| Version | Known advisories |
|---|---|
| AutoMapper 16.1.1 | CVE-2026-128082, CVE-2026-128081 |
| AutoMapper 16.1.0 | CVE-2026-128082, CVE-2026-128081, CVE-2026-32933 |
Which of your client projects are still on AutoMapper 16.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact AutoMapper version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other AutoMapper versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the NuGet registry. Refreshed daily.