GHSA-4r8w-73jc-3m7q
MEDIUMGHSA-4r8w-73jc-3m7q is a medium-severity (CVSS 6.1) Open Redirect vulnerability in org.springframework.security:spring-security-oauth2-authorization-server. O3 Security confirms whether GHSA-4r8w-73jc-3m7q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Spring Security OAuth2 Authorization Server: Authorization endpoint performs insufficient validation of the request_uri parameter
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-4r8w-73jc-3m7q.
Real-World Exposure
org.springframework.security:spring-security-oauth2-authorization-server☕org.springframework.security:spring-security-oauth2-authorization-serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Spring Security Authorization Server's authorization endpoint performs insufficient validation of the request_uri parameter. An attacker can craft a malicious authorization request containing an invalid request_uri and an arbitrary, unvalidated redirect_uri, which can lead to an Open Redirect vulnerability.
Affected versions: Spring Security 7.0.0 through 7.0.5. Spring Authorization Server 1.5.0 through 1.5.7.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.security:spring-security-oauth2-authorization-server | ≥ 7.0.0&&< 7.0.6 | 7.0.6 |
| ☕Maven | org.springframework.security:spring-security-oauth2-authorization-server | ≥ 1.5.0&&< 1.5.8 | 1.5.8 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security:spring-security-oauth2-authorization-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.springframework.security:spring-security-oauth2-authorization-server to 7.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4r8w-73jc-3m7q is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-4r8w-73jc-3m7q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-4r8w-73jc-3m7q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-4r8w-73jc-3m7q in your dependencies?
O3 detects GHSA-4r8w-73jc-3m7q across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.