AutoMapper
Affected
- introduced
16.0.0, fixed16.3.0(ecosystem)
Fixed versions
16.3.0
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-128081
AutoMapper: Denial of Service via uncontrolled recursion that bypasses MaxDepth
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
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.object or an interface aren't seen by self-reference detection, so the default limit isn't applied.Dictionary<string, object> or ExpandoObject (for example, deserialized JSON) onto typed destinations recurses with no depth tracking. MaxDepth has no effect.ConvertUsing that calls context.Mapper.Map ignores MaxDepth.Impact
An application that maps attacker-influenced, deeply nested data through one of these paths can be crashed. On a 1 MB stack (the Windows default), a few thousand levels of nesting are enough.
Fix
MaxDepth, and the default limit is applied to them.InsufficientExecutionStackException instead of overflowing.Workarounds
Set MaxDepth explicitly on derived maps and on maps reached through object or interface members. There is no configuration workaround for dictionary or dynamic sources, or for recursive type converters, other than limiting input depth before mapping.
Related
MaxDepth not enforced through constructor parameters and positional records, fixed in the same releases.High Basis: The source's own band: HIGH
16.0.0, fixed 16.3.0 (ecosystem)16.3.0
The export has no generic command for this ecosystem.
0, fixed 15.1.4 (ecosystem)15.1.4
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0