CVE-2026-76969 — @sap/cds-mtxs
CRITICALCVE-2026-76969 is a critical-severity (CVSS 9.4) CWE-522 vulnerability in @sap/cds-mtxs. A fix is available for @sap/cds-mtxs — see the affected versions and patch details below.
@sap/cds-mtx: Credential disclosure in multitenant applications using SAP Cloud Application Programming Model (CAP)
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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 CVE-2026-76969.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-76969 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,415 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@sap/cds-mtxsnpmDescription
@sap/cds-mtxs NPM library does not perform sufficient checks on certain functionality used in multitenant CAP applications with extensibility enabled. An unauthenticated attacker could send specially crafted requests to obtain sensitive credentials and abuse them to replace or delete tenant data. Successful exploitation can result in a high impact on availability and integrity of the application. There may also be partial impact to the confidentiality of business data.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @sap/cds-mtxs | ≥ 4.0.1&&< 4.0.3 | 4.0.3npm install @sap/cds-mtxs@4.0.3 |
| 📦npm | @sap/cds-mtxs | ≥ 3.0.1&&< 3.9.7 | 3.9.7npm install @sap/cds-mtxs@3.9.7 |
| 📦npm | @sap/cds-mtxs | ≥ 2.0.2&&< 2.7.7 | 2.7.7npm install @sap/cds-mtxs@2.7.7 |
| 📦npm | @sap/cds-mtxs | all versions | 1.18.4npm install @sap/cds-mtxs@1.18.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @sap/cds-mtxs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @sap/cds-mtxs to 4.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-76969 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
Is CVE-2026-76969 in your dependencies?
Find it across npm, including transitive dependencies.