CVE-2026-59281: Spring Framework Cross-site Scripting via EscapedErrors

Published Aug 27, 2026
·
Updated

Spring MVC and WebFlux applications that obtain a data-binding Errors instance with HTML escaping enabled and then render field errors using the no-argument Errors.getFieldErrors() or Errors.getFieldError() accessors are vulnerable to arbitrary HTML/JavaScript code injection, potentially resulting in a reflected cross-site scripting (XSS) vulnerability. Spring Framework 7.0.0 - 7.0.8 Spring Framework 6.2.0 - 6.2.19 Spring Framework 6.1.0 - 6.1.28 Spring Framework 6.0.0 - 6.0.30 Spring Framework 5.3.0 - 5.3.49 Spring Framework 5.2.25.RELEASE and earlier

Affected Software

6 affected components
Spring Spring Framework>=7.0.0<=7.0.8
Spring Spring Framework>=6.2.0<=6.2.19
Spring Spring Framework>=6.1.0<=6.1.28
Spring Spring Framework>=6.0.0<=6.0.30
Spring Spring Framework>=5.3.0<=5.3.49
Spring Spring Framework<=5.2.25.RELEASE

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Spring Framework to a version that resolves this vulnerability.

    Fixed in 5.2.25.RELEASE
  2. Upgrade

    Upgrade Spring Framework to a version that resolves this vulnerability.

    Fixed in 5.3.49
  3. Upgrade

    Upgrade Spring Framework to a version that resolves this vulnerability.

    Fixed in 6.0.30
  4. Upgrade

    Upgrade Spring Framework to a version that resolves this vulnerability.

    Fixed in 6.1.28
  5. Upgrade

    Upgrade Spring Framework to a version that resolves this vulnerability.

    Fixed in 6.2.19
  6. Upgrade

    Upgrade Spring Framework to a version that resolves this vulnerability.

    Fixed in 7.0.8

Event History

Aug 27, 2026
CVE Published
via MITRE·05:57 PM
Data Sourced
via MITRE·05:57 PM
DescriptionWeakness
Data Sourced
via NVD·08:17 PM
Description

Frequently Asked Questions

1

Which applications are exposed to this issue?

Spring MVC and WebFlux applications are affected when they obtain a data-binding Errors instance with HTML escaping enabled and render field errors through the no-argument Errors.getFieldErrors() or Errors.getFieldError() methods.

2

What must an attacker be able to do to exploit it?

An attacker must be able to supply input that reaches data binding and is subsequently included in field-error rendering through the affected no-argument accessors. Successful exploitation can inject arbitrary HTML or JavaScript into the rendered response, creating a reflected XSS risk.

3

Which Spring Framework versions are affected?

Affected releases are 7.0.0 through 7.0.8, 6.2.0 through 6.2.19, 6.1.0 through 6.1.28, 6.0.0 through 6.0.30, 5.3.0 through 5.3.49, and 5.2.25.RELEASE and earlier.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203