Update dependency AutoMapper to v15 [SECURITY]#107
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/nuget-automapper-vulnerability
branch
from
March 31, 2026 10:00
53e682c to
2674715
Compare
renovate
Bot
force-pushed
the
renovate/nuget-automapper-vulnerability
branch
from
April 13, 2026 09:46
2674715 to
706093f
Compare
renovate
Bot
force-pushed
the
renovate/nuget-automapper-vulnerability
branch
from
April 27, 2026 15:38
706093f to
23eb634
Compare
renovate
Bot
force-pushed
the
renovate/nuget-automapper-vulnerability
branch
3 times, most recently
from
May 12, 2026 07:34
c8fe950 to
6d2b46a
Compare
renovate
Bot
force-pushed
the
renovate/nuget-automapper-vulnerability
branch
2 times, most recently
from
May 20, 2026 14:52
b2ed466 to
aa0b503
Compare
renovate
Bot
force-pushed
the
renovate/nuget-automapper-vulnerability
branch
from
May 30, 2026 15:31
aa0b503 to
8c79602
Compare
renovate
Bot
force-pushed
the
renovate/nuget-automapper-vulnerability
branch
from
June 15, 2026 13:30
8c79602 to
6cd41b2
Compare
renovate
Bot
force-pushed
the
renovate/nuget-automapper-vulnerability
branch
5 times, most recently
from
June 29, 2026 14:37
7263b22 to
76213f8
Compare
renovate
Bot
force-pushed
the
renovate/nuget-automapper-vulnerability
branch
from
July 4, 2026 03:10
76213f8 to
ee0a2fc
Compare
renovate
Bot
force-pushed
the
renovate/nuget-automapper-vulnerability
branch
2 times, most recently
from
July 13, 2026 13:07
594d280 to
f43e2de
Compare
renovate
Bot
force-pushed
the
renovate/nuget-automapper-vulnerability
branch
from
July 18, 2026 04:15
f43e2de to
f6e611b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
14.0.0→15.1.3AutoMapper Vulnerable to Denial of Service (DoS) via Uncontrolled Recursion
CVE-2026-32933 / GHSA-rvv3-g6hj-g44x
More information
Details
Summary
AutoMapper is vulnerable to a Denial of Service (DoS) attack. When mapping deeply nested object graphs, the library uses recursive method calls without enforcing a default maximum depth limit. This allows an attacker to provide a specially crafted object graph that exhausts the thread's stack memory, triggering a
StackOverflowExceptionand causing the entire application process to terminate.Description
The vulnerability exists in the core mapping engine. When a source object contains a property of the same type (or a type that eventually points back to itself), AutoMapper recursively attempts to map each level.
Because there is no default limit on how many levels deep this recursion can go, a sufficiently nested object (approximately 25,000+ levels in standard .NET environments) will exceed the stack size. Since
StackOverflowExceptioncannot be caught in modern .NET runtimes, the application cannot recover and will crash immediately.Impact
Proof of Concept (PoC)
The following C# code demonstrates the crash by creating a nested "Circular" object graph and attempting to map it:
Recommended Mitigation
MaxDepth(e.g., 32 or 64) for all mapping operations.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
LuckyPennySoftware/AutoMapper (AutoMapper)
v15.1.3What's Changed
Security
Fixed an issue where certain cyclic or self-referential object graphs could trigger uncontrolled recursion during mapping, potentially resulting in stack exhaustion and denial of service.
Applications that process untrusted or attacker-controlled object graphs through affected mapping paths may be impacted.
Users should upgrade to this release.
Security advisory: GHSA-rvv3-g6hj-g44x
Thanks to @skdishansachin for responsibly disclosing this issue.
Full Changelog: LuckyPennySoftware/AutoMapper@v15.1.0...v15.1.3
v15.1.2What's Changed
Security
Fixed an issue where certain cyclic or self-referential object graphs could trigger uncontrolled recursion during mapping, potentially resulting in stack exhaustion and denial of service.
Applications that process untrusted or attacker-controlled object graphs through affected mapping paths may be impacted.
Users should upgrade to this release.
Security advisory: GHSA-rvv3-g6hj-g44x
Thanks to @skdishansachin for responsibly disclosing this issue.
Full Changelog: LuckyPennySoftware/AutoMapper@v16.1.1...v15.1.2
v15.1.1What's Changed
Security
Fixed an issue where certain cyclic or self-referential object graphs could trigger uncontrolled recursion during mapping, potentially resulting in stack exhaustion and denial of service.
Applications that process untrusted or attacker-controlled object graphs through affected mapping paths may be impacted.
Users should upgrade to this release.
Security advisory: GHSA-rvv3-g6hj-g44x
Thanks to @skdishansachin for responsibly disclosing this issue.
Full Changelog: LuckyPennySoftware/AutoMapper@v16.1.1...v15.1.1
v15.1.0What's Changed
New Contributors
Full Changelog: LuckyPennySoftware/AutoMapper@v15.0.1...v15.1.0
v15.0.1What's Changed
Full Changelog: LuckyPennySoftware/AutoMapper@v15.0.0...v15.0.1
This release supersedes the 15.0.0 release, reverting behavior and overloads so that the
AddAutoMapperoverloads separate the "scanning for maps" from the "scanning for dependencies". Unfortunately it's not really possible to combine these two together.This also fixes a critical bug in #4545 that does not work with .NET 4.x applications (as intended).
Because of this, the 15.0.0 will be delisted because of the breaking changes there.
v15.0.0Full Changelog: LuckyPennySoftware/AutoMapper@v14.0.0...v15.0.0
To set your license key:
This also introduced a breaking change with
MapperConfigurationrequiring anILoggerFactoryfor logging purposes:Registering AutoMapper with
services.AddAutoMapperwill automatically supply this parameter. Otherwise you'll need to supply the logger factory.You can obtain your license key at AutoMapper.io
Configuration
📅 Schedule: (in timezone Europe/London)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.