{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-59316 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-59316 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-59316 is a high-severity cross-site scripting vulnerability in Spring Authorization Server, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-59316 and fix it if it is affected.\n\nWhat it is: CVE-2026-59316 is a high-severity cross-site scripting vulnerability in Spring Authorization Server, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-59316 in the wild and no public exploit code.\n\nAffected product: Spring Authorization Server. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-59316/ (Markdown: https://insights.sbomify.com/CVE-2026-59316/index.md)","id":"CVE-2026-59316","markdown":"https://insights.sbomify.com/CVE-2026-59316/index.md","name":"CVE-2026-59316","record":{"aliases":["GHSA-5pc3-v4c3-6pv4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Spring Authorization Server","requires_auth":"none","summary":"Attackers can inject malicious scripts into the default consent page via crafted OAuth2 requests, potentially compromising user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"spring_authorization_server","vendor":"broadcom"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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.\nSpring Authorization Server 1.5.0 - 1.5.8\nSpring Authorization Server 1.4.0 - 1.4.11","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Spring Authorization Server Default Consent Page is vulnerable to Cross-Site Scripting (XSS)","id":"CVE-2026-59316","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in Spring for Apache Kafka","id":"CVE-2026-59317"},"packages":[],"prev":{"headline":"Spring Cloud Config Monitor Denial of Service","id":"CVE-2026-59315"},"products":["Spring Authorization Server"],"published":"2026-08-27","related":[{"cvss_score":9.6,"headline":"Auth bypass in Spring Authorization Server","id":"CVE-2026-22752","kev_date_added":null,"published":"2026-07-16"},{"cvss_score":6.1,"headline":"Spring Authorization Server: Open Redirect via request_uri parameter","id":"CVE-2026-59355","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":6.1,"headline":"Spring Security Authorization Server Open Redirect via request_uri","id":"CVE-2026-41008","kev_date_added":null,"published":"2026-06-09"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-28","vendors":["Spring"]},"summary":"Attackers can inject malicious scripts into the default consent page via crafted OAuth2 requests, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2026-59316/"}