GHSA-59c9-pxq8-9c73 is a critical-severity (CVSS 9.1) CWE-749 vulnerability in com.sap.cloud.security:java-security. O3 Security confirms whether GHSA-59c9-pxq8-9c73 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Improper JWT Signature Validation in SAP Security Services Library
Real-World Exposure
com.sap.cloud.security:java-security☕com.sap.cloud.security:java-security☕com.sap.cloud.security:spring-security☕com.sap.cloud.security:spring-security☕com.sap.cloud.security.xsuaa:spring-xsuaa☕com.sap.cloud.security.xsuaa:spring-xsuaaReal-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
Impact
SAP BTP Security Services Integration Library ([Java] cloud-security-services-integration-library) allows under certain conditions an escalation of privileges. On successful exploitation, an unauthenticated attacker can obtain arbitrary permissions within the application.
Patches
Upgrade to patched version >= 2.17.0 or >= 3.3.0 We always recommend to upgrade to the latest released version.
Workarounds
No workarounds
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.sap.cloud.security:java-security | all versions | 2.17.0 |
| ☕Maven | com.sap.cloud.security:java-security | ≥ 3.0.0&&< 3.3.0 | 3.3.0 |
| ☕Maven | com.sap.cloud.security:spring-security | all versions | 2.17.0 |
| ☕Maven | com.sap.cloud.security:spring-security | ≥ 3.0.0&&< 3.3.0 | 3.3.0 |
| ☕Maven | com.sap.cloud.security.xsuaa:spring-xsuaa | all versions | 2.17.0 |
| ☕Maven | com.sap.cloud.security.xsuaa:spring-xsuaa | ≥ 3.0.0&&< 3.3.0 | 3.3.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.sap.cloud.security:java-security. 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 com.sap.cloud.security:java-security to 2.17.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-59c9-pxq8-9c73 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-59c9-pxq8-9c73 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-59c9-pxq8-9c73. 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-59c9-pxq8-9c73 in your dependencies?
O3 detects GHSA-59c9-pxq8-9c73 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.