Version
.net6
lite is 4.14
Describe the bug
This CVE was fixed in 5.0.13 but we cannot migrate yet to 5.x. The CVE is a show stopper for some of our customers.
Expected behavior
Fix the CVE in v4
Additional context
Can we backport the CVE fix that was provided?
Here is an attempt