npm package report

Is @sap/xssec safe?

Q: Is @sap/xssec safe to install?

CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for @sap/xssec (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.

Q: Does @sap/xssec have known vulnerabilities?

Yes. CyberXYZ records 1 known vulnerability for @sap/xssec (npm), the worst rated CRITICAL. They are GHSA-p2vx-qj66-88q3.

Q: Which version of @sap/xssec should I use?

3.6.0 or later clears every advisory recorded for @sap/xssec (npm). Check the release you pick before installing it.

Q: How do I check @sap/xssec before installing?

Search @sap/xssec in CyberXYZ Check at https://cyberxyz.io/check?q=%40sap%2Fxssec. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.

@sap/xssec (npm) has 1 known vulnerability, the worst rated CRITICAL. Upgrade to 3.6.0 or later to clear it. No malicious-package signal is recorded.

// reach

2 direct dependencies

1 carry known advisories, worst HIGH

debugHIGH

1 packages depend on it

an advisory here reaches each of them

@sap-cloud-sdk/connectivity

Create a free accountfor every dependency path, dependent and what to upgrade

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

cvss

9.1

critical

CVSS v3.1 base score out of 10

epss

1.1%

medium

chance of exploitation in 30 days, 66th percentile of all CVEs

xyz score

4.6

medium

CyberXYZ composite out of 10

fig. 01 — GHSA-p2vx-qj66-88q3, the advisory selected below

// 1 advisories

GHSA-p2vx-qj66-88q3

CRITICALGitHub ratingCVE-2023-49583

SAP BTP Security Services Integration Library ([Node.js] @sap/xssec - versions < 3.6.0, allow under certain conditions an escalation of privileges.

Full advisory text at GitHub advisory or NVD.

// cvss v3.1 vector

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

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

// questions

Is @sap/xssec safe to install?

CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for @sap/xssec (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.

Does @sap/xssec have known vulnerabilities?

Yes. CyberXYZ records 1 known vulnerability for @sap/xssec (npm), the worst rated CRITICAL. They are GHSA-p2vx-qj66-88q3.

Which version of @sap/xssec should I use?

3.6.0 or later clears every advisory recorded for @sap/xssec (npm). Check the release you pick before installing it.

How do I check @sap/xssec before installing?

Search @sap/xssec in CyberXYZ Check at https://cyberxyz.io/check?q=%40sap%2Fxssec. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.

Checked 2026-11-14 at 11:52 UTC. The most recent advisory here was published 2023-12-12. Updated continuously from NVD, GHSA, OSV and CNA feeds.