{"answers":{"affected":"2 open source packages ship an affected version, including node and node-min. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-48615 in the wild and no public exploit code.","fix":"Upgrade node to a fixed version for your release line: 22.23.0, 24.17.0 or 26.3.1.","what":"CVE-2026-48615 is a medium-severity vulnerability in Nodejs Node.js, published on 26 Jun 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-48615 and fix it if it is affected.\n\nWhat it is: CVE-2026-48615 is a medium-severity vulnerability in Nodejs Node.js, published on 26 Jun 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-48615 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- node (Bitnami): affected from 22.22.3; fixed in 22.23.0, 24.17.0, 26.3.1\n- node-min (Bitnami): affected from 22.22.3; fixed in 22.23.0, 24.17.0, 26.3.1\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-48615/ (Markdown: https://insights.sbomify.com/CVE-2026-48615/index.md)","id":"CVE-2026-48615","markdown":"https://insights.sbomify.com/CVE-2026-48615/index.md","name":"CVE-2026-48615","record":{"aliases":["ALPINE-CVE-2026-48615","AZL-91230","BELL-CVE-2026-48615","BIT-node-2026-48615","BIT-node-min-2026-48615","DEBIAN-CVE-2026-48615","ECHO-117a-9a28-6844","GHSA-qqjm-7pv6-7q82","MINI-3wcr-h7r6-9p79","MINI-fmcj-wq7p-p234","MINI-w36v-qqj8-cc6v","UBUNTU-CVE-2026-48615"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js runtime","requires_auth":"none","summary":"Attackers can expose proxy credentials via error messages in Node.js, potentially leading to credential theft if logs are accessible.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"node.js","vendor":"nodejs"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-359","name":"Exposure of Private Personal Information to an Unauthorized Actor"}],"description":"A flaw in Node.js proxy tunnel error handling could expose proxy credentials in `ERR_PROXY_TUNNEL` error messages.\r\n\r\nWhen proxy credentials are embedded in the proxy URL, they may be exposed through error handling paths and captured by logs, diagnostics, or other error consumers.\r\n\r\nThis vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.","ecosystems":["Bitnami"],"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":"Information disclosure in node","id":"CVE-2026-48615","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"nodejs:node.js","products":["nodejs:node.js"],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Missing authorization in Rocket.Chat","id":"CVE-2026-48616"},"packages":[{"ecosystem":"Bitnami","fixed":["22.23.0","24.17.0","26.3.1"],"introduced":["22.22.3","24.16.0","26.3.0"],"last_affected":[],"package":"node","purl":"pkg:bitnami/node","source":"BIT-node-2026-48615"},{"ecosystem":"Bitnami","fixed":["22.23.0","24.17.0","26.3.1"],"introduced":["22.22.3","24.16.0","26.3.0"],"last_affected":[],"package":"node-min","purl":"pkg:bitnami/node-min","source":"BIT-node-min-2026-48615"}],"prev":{"headline":"Code injection in Plesk","id":"CVE-2026-48614"},"products":["node"],"published":"2026-06-26","related":[{"cvss_score":9.8,"headline":"Security feature bypass in Node","id":"CVE-2023-32002","kev_date_added":null,"published":"2023-08-21"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2016-6303","kev_date_added":null,"published":"2016-09-16"},{"cvss_score":9.1,"headline":"Security feature bypass in Node.js","id":"CVE-2017-15896","kev_date_added":null,"published":"2017-12-11"},{"cvss_score":8.8,"headline":"Server-side request forgery in Node.js","id":"CVE-2018-7160","kev_date_added":null,"published":"2018-05-17"},{"cvss_score":8.1,"headline":"Misconfiguration in Node.js","id":"CVE-2018-12120","kev_date_added":null,"published":"2018-11-28"},{"cvss_score":7.9,"headline":"Path traversal in Node","id":"CVE-2024-21891","kev_date_added":null,"published":"2024-02-20"},{"cvss_score":7.9,"headline":"Path traversal in Node","id":"CVE-2024-21896","kev_date_added":null,"published":"2024-02-20"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-06-26","vendors":["nodejs"]},"summary":"Attackers can expose proxy credentials via error messages in Node.js, potentially leading to credential theft if logs are accessible.","url":"https://insights.sbomify.com/CVE-2026-48615/"}