Information Disclosure vulnerability in SAP Cloud SDK for AI(JavaScript)
Affects @sap-ai-sdk/ai-api up to and including 2.17.0 in SAP Cloud SDK for AI (JavaScript), under specific failure conditions. Fixed in 2.18.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected versions: @sap-ai-sdk/ai-api up to and including 2.17.0; patched in 2.18.0 Requires certain internal operations to hit specific failure conditions that generate error messages
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.28% · 20th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 21/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The SAP Cloud SDK for AI for JavaScript (Node.js) can include sensitive authentication credentials in error messages under certain failure conditions. An attacker over the network with low-privilege login could read these credentials from application logs or forwarded error output and reuse them against the associated SAP service, gaining high confidentiality, integrity, and availability impact.
Read the original description
SAP Cloud SDK for AI (Node.js) could inadvertently include sensitive authentication credentials in error messages generated by certain internal operations under specific failure conditions. An attacker with low privileges and access to application logs or forwarded error output could obtain these credentials, but only after waiting for a suitable failure event triggered by a higher-privileged user and within the limited lifetime of the token, making exploitation complex. Successful exploitation could allow the attacker to reuse the disclosed credentials against the associated SAP service, resulting in a high impact on confidentiality, integrity and availability.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch5/5No patch listed yet
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 28 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected versions: @sap-ai-sdk/ai-api up to and including 2.17.0; patched in 2.18.0 Requires certain internal operations to hit specific failure conditions that generate error messagesWorkaround: The available data does not list a workaround. Until the upgrade is applied, limit where error output from the SDK is written or forwarded, since the credentials appear in error messages.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-120012 (Information Disclosure vulnerability in SAP Cloud SDK for AI(JavaScript)), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-120012 (entry last updated 2026-11-10): Affected: - SAP_SE SAP Cloud SDK for AI(JavaScript): through v2.17.0 Fixed versions: none listed yet. Conditions (all must be true for the bug to be hit): - Affected versions: @sap-ai-sdk/ai-api up to and including 2.17.0; patched in 2.18.0 (source: https://github.com/SAP/ai-sdk-js/security/advisories/GHSA-8g7j-49xg-8wf3) - Requires certain internal operations to hit specific failure conditions that generate error messages (source: https://github.com/SAP/ai-sdk-js/security/advisories/GHSA-8g7j-49xg-8wf3) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, low-privilege login, no user action. CISA KEV: CVE-2026-120012 is not listed as of cve.now's last read. This KEV status is for CVE-2026-120012 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/SAP/ai-sdk-js/security/advisories/GHSA-8g7j-49xg-8wf3 - https://url.sap/sapsecuritypatchday Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-120012 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-120012.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- SAP_SE SAP Cloud SDK for AI(JavaScript)
through v2.17.0
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120012
Is CVE-2026-120012 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Under specific failure conditions, certain internal operations can include sensitive authentication credentials, namely a destination token, in error messages. Those messages can end up in logs or forwarded error output. The disclosed credentials could then be reused against the associated SAP service.Source: github.com
Which versions are affected by CVE-2026-120012?
SAP Cloud SDK for AI(JavaScript): through v2.17.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions of @sap-ai-sdk/ai-api up to and including 2.17.0 are affected, and 2.18.0 is patched. To check an installed version, look at the @sap-ai-sdk/ai-api entry in package.json or the lockfile, or run npm ls @sap-ai-sdk/ai-api.Source: github.com
How do I fix CVE-2026-120012?
Upgrade @sap-ai-sdk/ai-api to 2.18.0 or later.Source: github.com
What if there's no patch?
The available data does not list a workaround. Until the upgrade is applied, limit where error output from the SDK is written or forwarded, since the credentials appear in error messages.Source: github.com