VulnerabilityPublished 13 Nov 2026

CVE-2026-128082: AutoMapper · Uncontrolled Recursion with Constructor Parameters

Affects AutoMapperSource GCVE Database

Compare

Mentioned vulnerabilities

CVE-2026-32933

Authoritative record:CVE-2026-128082· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 16.3.0 soon.

Data as of 13 Nov 2026, 20:18 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	7.5

Patch: Available – fixed in 16.3.0, 15.1.4

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade AutoMapper to 16.3.0; AutoMapper to 15.1.4.

Affected software

Product	Affected	Fixed in
NuGetAutoMapper	Affected >=16.0.0 <16.3.0	Fixed in 16.3.0
NuGetAutoMapper	Affected <15.1.4	Fixed in 15.1.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade AutoMapper to version 16.3.0 or later, or 15.1.4 or later, where the issue is fixed. For destination types with parameterless constructors, disabling constructor mapping via cfg.DisableConstructorMapping() enforces MaxDepth on property mapping and can serve as a workaround. For positional records or types without parameterless constructors, limit input nesting depth before mapping or upgrade. No other effective workaround exists.

Description

AutoMapper versions prior to 16.3.0 and before 15.1.4 have a vulnerability where the MaxDepth recursion limit is not enforced when mapping destination types constructed via constructor parameters, such as positional records. This leads to uncontrolled recursion and a StackOverflowException that terminates the process. The flaw bypasses the MaxDepth mitigation introduced for a related vulnerability (CVE-2026-32933).

Impact

Applications using vulnerable AutoMapper versions that map deeply nested, attacker-controlled data to destination types constructed via constructor parameters can be crashed by unbounded recursion leading to a StackOverflowException. This exception is uncatchable and causes process termination, resulting in denial of service. The vulnerability bypasses existing MaxDepth protections, increasing risk for applications relying on this mitigation.

Summary

The vulnerability in AutoMapper arises because the MaxDepth recursion limit is only incremented after the destination object is created. When mapping destination types through constructor parameters, including positional records, the recursion occurs during object creation before the depth counter increments. This allows deeply nested source objects to be mapped without triggering the MaxDepth limit, causing unbounded recursion and a StackOverflowException. The issue affects mappings with explicit MaxDepth settings and the default limit of 64. It was fixed in AutoMapper versions 16.3.0 and 15.1.4 by counting depth before object creation to enforce the limit uniformly. Workarounds include disabling constructor mapping for destination types with parameterless constructors, but positional records have no workaround other than input depth limiting or upgrading.

CWE-674Uncontrolled Recursion (opens in a new tab)
Class weakness
The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.
Implementation
Ensure that an end condition will be reached under all logic conditions. The end condition may include checking against the depth of recursion and exiting with an error if the recursion goes too deep. The complexity of the end condition contributes to the effectiveness of this action.
Implementation
Increase the stack size.
Attack patterns
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 20:18 UTC

WeaknessesCWE-674

Technical details

References

Community reviews

Related threats