Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

AutoMapper: Denial of Service via uncontrolled recursion that bypasses MaxDepth

CVE-2026-128081GHSA-gpwp-5797-mjff

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (automapper 16.3.0, 15.1.4), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • NuGet automapper

    Affected
    >= 16.0.0, < 16.3.0< 15.1.4
    Fixed in
    15.1.4, 16.3.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-128081: 0.55% estimated exploitation activity in the next 30 days; percentile 46.30 (FIRST EPSS, 2026-11-14). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The default and explicit `MaxDepth` limits added for CVE-2026-32933 don't apply to several mapping paths. Mapping a deeply nested source through any of them recurses without bound and throws a `StackOverflowException`, which can't be caught and terminates the process.

Affected paths - Polymorphic maps: derived type maps (`Include` / `IncludeBase`) didn't inherit the base map's `MaxDepth`, and the default limit for self-referential maps was only applied to the base map. A chain of derived objects was mapped without a limit, even with `MaxDepth` set on the base map. - Runtime-typed members: members typed as `object` or an interface aren't seen by self-reference detection, so the default limit isn't applied. - Dictionary and dynamic sources: mapping a nested `Dictionary ` or `ExpandoObject` (for example, deserialized JSON) onto typed destinations recurses with no depth tracking. `MaxDepth` has no effect. - Recursive type converters: `ConvertUsing` that…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-gpwp-5797-mjff

  2. Revision 1 · created ·

    Published from ghsa record GHSA-gpwp-5797-mjff

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-128081

Advisory: AutoMapper: Denial of Service via uncontrolled recursion that bypasses MaxDepth
IDs: CVE-2026-128081, GHSA-gpwp-5797-mjff
Record: https://patchnext.com/advisories/cve-2026-128081 (revision 2, source checked 14 Nov 2026, 08:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: automapper 16.3.0, 15.1.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet automapper: affected >= 16.0.0, < 16.3.0; < 15.1.4; fixed in 15.1.4, 16.3.0

## Suggested inspection (read-only)
- NuGet automapper: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on automapper.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gpwp-5797-mjff (GitHub-reviewed advisory GHSA-gpwp-5797-mjff lists affected ranges: NuGet automapper >=16.0.0 =0 <15.1.4)
- Verified: https://osv.dev/vulnerability/GHSA-gpwp-5797-mjff (OSV record GHSA-gpwp-5797-mjff lists affected ranges: NuGet automapper >=16.0.0 =0 <15.1.4 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…