VulnerabilityPublished 20 Mar 2026

CVE-2026-32933: LuckyPennySoftware AutoMapper · Uncontrolled Recursion

Affects LuckyPennySoftware AutoMapperSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 16.1.1 or 15.1.1 soon.

Data as of 1 Nov 2026, 08:20 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 16.1.1, 15.1.1

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 20 Mar 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 31 Oct 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 and automapper to 16.1.1 or 15.1.1.

Affected software

Product	Affected	Fixed in
LuckyPennySoftwareAutoMapper	Affected >=16.0.0 <16.1.1	Fixed in 16.1.1
LuckyPennySoftwareAutoMapper	Affected <15.1.1	Fixed in 15.1.1
NuGetautomapper`pkg:nuget/automapper`Other threats	Affected <15.1.1 >=16.0.0 <16.1.1	Fixed in 15.1.1 16.1.1

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

AI-suggested

To mitigate CVE-2026-32933, organizations should immediately upgrade AutoMapper to versions 15.1.1 or 16.1.1, where the vulnerability is fixed. If upgrading is not immediately feasible, implement input validation and sanitization to restrict the depth and complexity of object graphs processed by AutoMapper, thereby preventing excessive recursion. Developers should audit application code to identify all usage points of AutoMapper and ensure that untrusted or user-supplied data is not mapped without validation. Employ runtime monitoring and alerting for StackOverflowException or application crashes to detect potential exploitation attempts. Consider implementing circuit breakers or fallback mechanisms to maintain service availability during failures. Finally, maintain an inventory of .NET dependencies and apply timely patch management practices to reduce exposure to similar vulnerabilities.

Description

CVE-2026-32933 is a high-severity vulnerability in LuckyPennySoftware's AutoMapper library for . NET, affecting versions prior to 15.1.1 and between 16.0.0 and 16.1.1. The flaw arises from uncontrolled recursion when mapping deeply nested object graphs, leading to stack exhaustion and a StackOverflowException that crashes the application process. This Denial of Service (DoS) vulnerability requires no authentication or user interaction and can be triggered remotely by supplying crafted input.

Impact

The primary impact of CVE-2026-32933 is a Denial of Service condition caused by application crashes due to stack overflow. Organizations using vulnerable AutoMapper versions in their .NET applications may experience unexpected service outages, degraded user experience, and potential cascading failures if critical services depend on the affected components. This can disrupt business operations, especially for web applications, APIs, and backend services that rely on AutoMapper for data transformation. The vulnerability does not expose sensitive data or allow unauthorized code execution, but the loss of availability can have severe operational and reputational consequences. Enterprises with high-availability requirements or those operating in regulated industries may face compliance risks if service disruptions occur. Additionally, attackers could leverage this vulnerability as part of a broader attack chain to cause disruption or distract security teams.

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 27 Mar 2026, 19:34 UTC

WeaknessesCWE-674

Technical details

References

Community reviews

Related threats