Unauthorized access to data in @sap-cloud-sdk/core

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2021-41251: 1.71% estimated exploitation activity in the next 30 days; percentile 77.40 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact This affects applications on SAP Business Technology Platform that use the SAP Cloud SDK and enabled caching of destinations. In some cases, when user information was missing, destinations were cached without user information, allowing other users to retrieve the same destination with its permissions. By default, destination caching is disabled. If it is enabled the maximum lifetime is 5 minutes which limits the attack vector. Patches The problem was fixed by #1769 and #1770. The security for caching has been increased. The changes are released in version 1.52.0. Workarounds Disable destination caching (it is disabled by default). References destination cache API docs For more information If you have any questions or comments about this advisory: Open an issue in https://github.com/SAP/cloud-sdk-js

Published by the source

10 Nov 2021, 16:51 UTC

Last modified by the source

8 Jul 2026, 06:29 UTC

Source last checked

26 Oct 2026, 12:21 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-gp2f-254m-rh32

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-gp2f-254m-rh32

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-41251

Advisory: Unauthorized access to data in @sap-cloud-sdk/core
IDs: CVE-2021-41251, GHSA-gp2f-254m-rh32
Record: https://patchnext.com/advisories/cve-2021-41251 (revision 2, source checked 26 Oct 2026, 12:21 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @sap-cloud-sdk/core 1.52.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @sap-cloud-sdk/core: affected < 1.52.0; fixed in 1.52.0

## Suggested inspection (read-only)
- `npm ls @sap-cloud-sdk/core --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @sap-cloud-sdk/core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-gp2f-254m-rh32 (OSV record GHSA-gp2f-254m-rh32 lists affected ranges: npm @sap-cloud-sdk/core >=0 <1.52.0 (fixed))
- Verified: https://github.com/advisories/GHSA-gp2f-254m-rh32 (GitHub-reviewed advisory GHSA-gp2f-254m-rh32 lists affected ranges: npm @sap-cloud-sdk/core >=0 <1.52.0)

Commands are suggestions: review each one before running it.