Authenticated cross-site scripting via error response rendering
Published Jun 11, 2026 · Updated Jun 11, 2026
Cross-site scripting in Spring Web Flow 4.0.0, 3.0.0 through 3.0.1, and 2.5.0 through 2.5.1 allows remote authenticated users to run browser script. JavaScript RemotingHandler renders an Ajax error body as HTML without requiring a text/html Content-Type, allowing reflected attacker input to execute. Exposure requires spring-js-resources, Spring-Dojo.js for Ajax requests, an attacker-influenced server error, and user interaction.
Summary
What happened
Cross-site scripting in Spring Web Flow 4.0.0, 3.0.0 through 3.0.1, and 2.5.0 through 2.5.1 allows remote authenticated users to run browser script. JavaScript RemotingHandler renders an Ajax error body as HTML without requiring a text/html Content-Type, allowing reflected attacker input to execute. Exposure requires spring-js-resources, Spring-Dojo.js for Ajax requests, an attacker-influenced server error, and user interaction.
The record
- CVE
- CVE-2026-40986
- Published
- Jun 11, 2026
- Updated
- Jun 11, 2026
- Vendor
- Spring
- Product
- Spring Web Flow
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 11, 2026CVE publishedPublication date reported by the CVE source.
- Jun 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.5.0 <2.5.2
- Affected versionversion=3.0.0 <3.0.2
- Affected versionversion=4.0.0 <4.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo