Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-32933: CWE-674: Uncontrolled Recursion in LuckyPennySoftware AutoMapper

0
High
VulnerabilityCVE-2026-32933cvecve-2026-32933cwe-674
Published: Fri Mar 20 2026 (03/20/2026, 02:38:41 UTC)
Source: CVE Database V5
Vendor/Project: LuckyPennySoftware
Product: AutoMapper

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/27/2026, 19:34:45 UTC

Technical Analysis

AutoMapper is a widely used convention-based object-to-object mapping library in the .NET ecosystem, designed to simplify the transformation of data between different object models. CVE-2026-32933 identifies a vulnerability classified under CWE-674 (Uncontrolled Recursion) affecting AutoMapper versions prior to 15.1.1 and between 16.0.0 and 16.1.1. The root cause is the library's recursive approach to mapping deeply nested object graphs without enforcing a maximum recursion depth limit. When an attacker supplies a specially crafted object graph with excessive nesting, the recursive calls exhaust the thread's stack memory, resulting in a StackOverflowException. This exception causes the entire application process to terminate abruptly, leading to a Denial of Service (DoS) condition. The vulnerability does not impact confidentiality or integrity but severely affects availability. Exploitation requires no privileges or user interaction and can be triggered remotely if the application processes untrusted input through AutoMapper. The issue is resolved in versions 15.1.1 and 16.1.1 by introducing recursion depth limits or other safeguards to prevent stack exhaustion. No known exploits are currently reported in the wild, but the vulnerability's nature and ease of exploitation make it a significant risk for affected applications.

Potential 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.

Mitigation Recommendations

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.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-17T00:05:53.282Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69bcbde5e32a4fbe5f2545b6

Added to database: 3/20/2026, 3:24:21 AM

Last enriched: 3/27/2026, 7:34:45 PM

Last updated: 5/2/2026, 8:31:17 PM

Views: 587

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses