AutoMapper vulnerabilities

A convention-based object-object mapper.

Registry
NuGet
Latest
17.0.0

3 known advisories

The latest version, 17.0.0, is not affected by any of them. Projects on older versions may be.

Update to the latest version:dotnet add package AutoMapper --version 17.0.0

Is your project on an affected AutoMapper?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Security advisories for AutoMapper

  • HighCVE-2026-128082GHSA-6vhm-j9h7-f9gh13 Nov 2026

    AutoMapper: Uncontrolled Recursion with Constructor Parameters

    Affected
    >=16.0.0 <16.3.0 · <15.1.4
    Fixed in
    15.1.4, 16.3.0
  • HighCVE-2026-128081GHSA-gpwp-5797-mjff13 Nov 2026

    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
  • HighCVE-2026-32933GHSA-rvv3-g6hj-g44x13 Mar 2026

    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

Is your AutoMapper version vulnerable?

Which of your client projects still run an old AutoMapper?

NPMscan reads the packages.lock.json and .csproj files in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other NuGet packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the NuGet registry.