{"answers":{"affected":"4 open source packages ship an affected version, including @grpc/grpc-js.","exploited":"There is no known exploitation of CVE-2026-101915 in the wild and no public exploit code.","fix":"Upgrade @grpc/grpc-js to a fixed version for your release line: 1.13.6 or 1.14.5.","what":"CVE-2026-101915 is a low-severity vulnerability in grpc-node, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-101915 and fix it if it is affected.\n\nWhat it is: CVE-2026-101915 is a low-severity vulnerability in grpc-node, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-101915 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @grpc/grpc-js (npm): affected all versions; fixed in 1.13.6\n- @grpc/grpc-js (npm): affected all versions; fixed in 1.13.6\n- @grpc/grpc-js (npm): affected from 1.14.0; fixed in 1.14.5\n- @grpc/grpc-js (npm): affected from 1.14.0; fixed in 1.14.5\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-101915/ (Markdown: https://insights.sbomify.com/CVE-2026-101915/index.md)","id":"CVE-2026-101915","markdown":"https://insights.sbomify.com/CVE-2026-101915/index.md","name":"CVE-2026-101915","record":{"aliases":["CLEANSTART-2026-AF37624","CLEANSTART-2026-DP81887","CLEANSTART-2026-VD98265","CLEANSTART-2026-ZH62940","ECHO-2e1d-24f0-0a19","GHSA-f596-whhp-79r4","MINI-2fxm-4rv5-wfwq","MINI-4jg6-7mmp-64x9","MINI-57rr-gjxc-h4f8","MINI-76x8-m9hg-pcr4","MINI-8cfg-gqc6-fhcj","MINI-985w-82vm-2j62","MINI-c34v-6r6g-pm8r","MINI-f3hf-p7jh-wqw4","MINI-f8rf-gj5w-46w9","MINI-gpr6-7vh7-w695","MINI-h8v5-93w6-7h4x","MINI-m3qm-pj99-hm2c","MINI-rj7h-25wp-vv72","MINI-vpq7-65q4-xhj6","MINI-w365-3cv3-wc9w"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"gRPC JavaScript library","requires_auth":"none","summary":"Attackers can obtain sensitive information from error messages returned by gRPC server method handlers in the @grpc/grpc-js library.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-550","name":"Server-generated Error Message Containing Sensitive Information"}],"description":"@grpc/grpc-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to 1.13.6 and 1.14.5, when an application method handler throws an uncaught error, the server includes its error message in the status message sent to the client. The thrown error message is transmitted to the client, causing sensitive information disclosure when the message contains sensitive data. This issue is fixed in versions 1.13.6 and 1.14.5.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"@grpc/grpc-js: The server transmits some error messages thrown by method handlers to the client in status messages","id":"CVE-2026-101915","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":4,"n_references":6,"next":{"headline":"@grpc/grpc-js: In certain configurations, getAuthContext can return unauthorized certificates as though they were authorized","id":"CVE-2026-101916"},"packages":[{"ecosystem":"npm","fixed":["1.13.6"],"introduced":["0"],"last_affected":[],"package":"@grpc/grpc-js","purl":null,"source":"GHSA-f596-whhp-79r4"},{"ecosystem":"npm","fixed":["1.13.6"],"introduced":["0"],"last_affected":[],"package":"@grpc/grpc-js","purl":"pkg:npm/%40grpc/grpc-js","source":"GHSA-f596-whhp-79r4"},{"ecosystem":"npm","fixed":["1.14.5"],"introduced":["1.14.0"],"last_affected":[],"package":"@grpc/grpc-js","purl":null,"source":"GHSA-f596-whhp-79r4"},{"ecosystem":"npm","fixed":["1.14.5"],"introduced":["1.14.0"],"last_affected":[],"package":"@grpc/grpc-js","purl":"pkg:npm/%40grpc/grpc-js","source":"GHSA-f596-whhp-79r4"}],"prev":{"headline":"@grpc/grpc-js: The exact path match matcher incorrectly only applies a prefix match for case-insensitive matches","id":"CVE-2026-101914"},"products":["grpc-node"],"published":"2026-09-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-01","vendors":["grpc"]},"summary":"Attackers can obtain sensitive information from error messages returned by gRPC server method handlers in the @grpc/grpc-js library.","url":"https://insights.sbomify.com/CVE-2026-101915/"}