Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-gpwp-5797-mjff
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'sMaxDepth, 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 withMaxDepthset on the base map. - Runtime-typed members: members typed as
objector an interface aren't seen by self-reference detection, so the default limit isn't applied. - Dictionary and dynamic sources: mapping a nested
Dictionary<string, object>orExpandoObject(for example, deserialized JSON) onto typed destinations recurses with no depth tracking.MaxDepthhas no effect. - Recursive type converters:
ConvertUsingthat callscontext.Mapper.MapignoresMaxDepth.
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
- Derived type maps inherit
MaxDepth, and the default limit is applied to them. - Every runtime map call checks for sufficient stack, and fails with a catchable
InsufficientExecutionStackExceptioninstead 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
- CVE-2026-32933 (GHSA-rvv3-g6hj-g44x)
- GHSA-6vhm-j9h7-f9gh:
MaxDepthnot enforced through constructor parameters and positional records, fixed in the same releases.
Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.
Drag and drop some file here, or click to select
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the availability of the system.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard