Vmware Spring Framework up to 5.3.48/6.1.27/6.2.18/7.0.7 302 Redirect redirect

Summaryinfo

A vulnerability classified as problematic has been found in Vmware Spring Framework up to 5.3.48/6.1.27/6.2.18/7.0.7. Affected by this issue is some unknown functionality of the component 302 Redirect Handler. This manipulation causes redirect. This vulnerability appears as CVE-2026-41844. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in Vmware Spring Framework up to 5.3.48/6.1.27/6.2.18/7.0.7. It has been declared as problematic. Affected by this vulnerability is some unknown processing of the component 302 Redirect Handler. The manipulation with an unknown input leads to a redirect vulnerability. The CWE definition for the vulnerability is CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. As an impact it is known to affect integrity. The summary by CVE is:

A Spring MVC or Spring WebFlux application which configures a mapping for "/**" where the view name is not explicitly specified allows an attacker to craft a link resulting in a 302 redirect to an arbitrary external host via the redirect: prefix. Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.0 through 5.3.48.

It is possible to read the advisory at spring.io. This vulnerability is known as CVE-2026-41844 since 04/22/2026. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/09/2026). The attack technique deployed by this issue is T1204.001 according to MITRE ATT&CK.

Upgrading to version 5.3.49, 6.1.28, 6.2.19 or 7.0.8 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Vmware

Name

• Spring Framework

Version

• 5.3.0
• 5.3.1
• 5.3.2
• 5.3.3
• 5.3.4
• 5.3.5
• 5.3.6
• 5.3.7
• 5.3.8
• 5.3.9
• 5.3.10
• 5.3.11
• 5.3.12
• 5.3.13
• 5.3.14
• 5.3.15
• 5.3.16
• 5.3.17
• 5.3.18
• 5.3.19
• 5.3.20
• 5.3.21
• 5.3.22
• 5.3.23
• 5.3.24
• 5.3.25
• 5.3.26
• 5.3.27
• 5.3.28
• 5.3.29
• 5.3.30
• 5.3.31
• 5.3.32
• 5.3.33
• 5.3.34
• 5.3.35
• 5.3.36
• 5.3.37
• 5.3.38
• 5.3.39
• 5.3.40
• 5.3.41
• 5.3.42
• 5.3.43
• 5.3.44
• 5.3.45
• 5.3.46
• 5.3.47
• 5.3.48
• 6.1.0
• 6.1.1
• 6.1.2
• 6.1.3
• 6.1.4
• 6.1.5
• 6.1.6
• 6.1.7
• 6.1.8
• 6.1.9
• 6.1.10
• 6.1.11
• 6.1.12
• 6.1.13
• 6.1.14
• 6.1.15
• 6.1.16
• 6.1.17
• 6.1.18
• 6.1.19
• 6.1.20
• 6.1.21
• 6.1.22
• 6.1.23
• 6.1.24
• 6.1.25
• 6.1.26
• 6.1.27
• 6.2.0
• 6.2.1
• 6.2.2
• 6.2.3
• 6.2.4
• 6.2.5
• 6.2.6
• 6.2.7
• 6.2.8
• 6.2.9
• 6.2.10
• 6.2.11
• 6.2.12
• 6.2.13
• 6.2.14
• 6.2.15
• 6.2.16
• 6.2.17
• 6.2.18
• 7.0.0
• 7.0.1
• 7.0.2
• 7.0.3
• 7.0.4
• 7.0.5
• 7.0.6
• 7.0.7

License

• commercial

Website

• Vendor: https://www.vmware.com/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion