How severe is GHSA-59c9-pxq8-9c73?

GHSA-59c9-pxq8-9c73 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-59c9-pxq8-9c73?

GHSA-59c9-pxq8-9c73 affects the following packages: com.sap.cloud.security:java-security (Maven), com.sap.cloud.security:java-security (Maven), com.sap.cloud.security:spring-security (Maven), com.sap.cloud.security:spring-security (Maven), com.sap.cloud.security.xsuaa:spring-xsuaa (Maven), com.sap.cloud.security.xsuaa:spring-xsuaa (Maven). Ecosystems affected: Maven.

How do I fix GHSA-59c9-pxq8-9c73?

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.

How do I detect GHSA-59c9-pxq8-9c73 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.sap.cloud.security:java-security, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-59c9-pxq8-9c73 if there is no patch (or I can't update yet)?

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.

Is GHSA-59c9-pxq8-9c73 actively exploited in the wild?

No public exploit code has been indexed for GHSA-59c9-pxq8-9c73 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-59c9-pxq8-9c73?

GHSA-59c9-pxq8-9c73 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 71th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-59c9-pxq8-9c73?

GHSA-59c9-pxq8-9c73 is classified as CWE-749 (CWE-749). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-59c9-pxq8-9c73 published, and has it been updated?

GHSA-59c9-pxq8-9c73 was published on December 13, 2023 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

GHSA-59c9-pxq8-9c73 — java-security

CRITICALFix: SAP/cloud-security-services-integration-library@4b3e42a

GHSA-59c9-pxq8-9c73 is a critical-severity (CVSS 9.1) CWE-749 vulnerability in com.sap.cloud.security:java-security. A fix is available for com.sap.cloud.security:java-security — see the affected versions and patch details below.

Improper JWT Signature Validation in SAP Security Services Library

Also known asCVE-2023-50422 CVE-2023-50424 GHSA-92cg-ghq6-9587 GHSA-m8rw-rcpq-2vp2GO-2023-2400

Published

Dec 13, 2023

Updated

Jul 8, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs71th percentile — riskier than 71% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-59c9-pxq8-9c73 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

6 pkgs affected

☕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-xsuaa

Real-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

https://www.cve.org/CVERecord?id=CVE-2023-50422

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.sap.cloud.security:java-security`	all versions	2.17.0`com.sap.cloud.security:java-security:2.17.0`
☕Maven	`com.sap.cloud.security:java-security`	≥ 3.0.0&&< 3.3.0	3.3.0`com.sap.cloud.security:java-security:3.3.0`
☕Maven	`com.sap.cloud.security:spring-security`	all versions	2.17.0`com.sap.cloud.security:spring-security:2.17.0`
☕Maven	`com.sap.cloud.security:spring-security`	≥ 3.0.0&&< 3.3.0	3.3.0`com.sap.cloud.security:spring-security:3.3.0`
☕Maven	`com.sap.cloud.security.xsuaa:spring-xsuaa`	all versions	2.17.0`com.sap.cloud.security.xsuaa:spring-xsuaa:2.17.0`
☕Maven	`com.sap.cloud.security.xsuaa:spring-xsuaa`	≥ 3.0.0&&< 3.3.0	3.3.0`com.sap.cloud.security.xsuaa:spring-xsuaa:3.3.0`

Affected Products

1 product · 2 configurations

Application

cloud-security-services-integration-librarysap

≥ 3.0.0 && < 3.3.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.sap.cloud.security:java-security, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.

Frequently Asked Questions

### 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 https://www.cve.org/CVERecord?id=CVE-2023-50422