{"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-48617 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-48617 is a low-severity vulnerability in Nodejs Node.js, published on 18 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-48617 and fix it if it is affected.\n\nWhat it is: CVE-2026-48617 is a low-severity vulnerability in Nodejs Node.js, published on 18 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-48617 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- node (Bitnami): affected all versions; fixed in 22.23.0, 24.17.0, 26.3.1\n- node-min (Bitnami): affected all versions; 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-48617/ (Markdown: https://insights.sbomify.com/CVE-2026-48617/index.md)","id":"CVE-2026-48617","markdown":"https://insights.sbomify.com/CVE-2026-48617/index.md","name":"CVE-2026-48617","record":{"aliases":["ALPINE-CVE-2026-48617","AZL-91124","BELL-CVE-2026-48617","BIT-node-2026-48617","BIT-node-min-2026-48617","DEBIAN-CVE-2026-48617","ECHO-7ecc-9369-9e95","GHSA-rv82-5vqw-69hj","MINI-3925-w8xq-q732","MINI-4mh2-2276-8gcf","MINI-666j-ghqh-w332","MINI-6w7m-g4mv-x28h","MINI-89gm-46mc-q8xh","MINI-f9qg-xc7f-f9f2","MINI-pxcj-x3hg-7hvx","MINI-rpxf-pppr-mjx8","RHSA-2026:46197","UBUNTU-CVE-2026-48617"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Node.js runtime","requires_auth":"high_privilege","summary":"Attackers can bypass Node.js Permission Model restrictions via process.report.writeReport() path misvalidation, potentially accessing protected data.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"node.js","vendor":"nodejs"}],"cvss":{"score":1.8,"severity":"low","source":"cna","vector":"CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"A flaw in Node.js Permission Model enforcement allows Bypass via `process.report.writeReport()` Path Misvalidation. This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.","ecosystems":["Bitnami","Red Hat:hummingbird:1"],"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":"Security feature bypass in node","id":"CVE-2026-48617","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"nodejs:node.js","products":["nodejs:node.js"],"type":"security_feature_bypass","year":"2026"},"n_packages":10,"n_references":2,"next":{"headline":"Security feature bypass in node","id":"CVE-2026-48618"},"packages":[{"ecosystem":"Bitnami","fixed":["22.23.0","24.17.0","26.3.1"],"introduced":["0","23.0.0","25.0.0"],"last_affected":[],"package":"node","purl":"pkg:bitnami/node","source":"BIT-node-2026-48617"},{"ecosystem":"Bitnami","fixed":["22.23.0","24.17.0","26.3.1"],"introduced":["0","23.0.0","25.0.0"],"last_affected":[],"package":"node-min","purl":"pkg:bitnami/node-min","source":"BIT-node-min-2026-48617"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:24.18.0-0.6.hum1"],"introduced":["0"],"last_affected":[],"package":"nodejs24","purl":"pkg:rpm/redhat/nodejs24","source":"RHSA-2026:46197"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:24.18.0-0.6.hum1"],"introduced":["0"],"last_affected":[],"package":"nodejs24-bin","purl":"pkg:rpm/redhat/nodejs24-bin","source":"RHSA-2026:46197"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:24.18.0-0.6.hum1"],"introduced":["0"],"last_affected":[],"package":"nodejs24-devel","purl":"pkg:rpm/redhat/nodejs24-devel","source":"RHSA-2026:46197"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:24.18.0-0.6.hum1"],"introduced":["0"],"last_affected":[],"package":"nodejs24-docs","purl":"pkg:rpm/redhat/nodejs24-docs","source":"RHSA-2026:46197"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:24.18.0-0.6.hum1"],"introduced":["0"],"last_affected":[],"package":"nodejs24-full-i18n","purl":"pkg:rpm/redhat/nodejs24-full-i18n","source":"RHSA-2026:46197"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:24.18.0-0.6.hum1"],"introduced":["0"],"last_affected":[],"package":"nodejs24-libs","purl":"pkg:rpm/redhat/nodejs24-libs","source":"RHSA-2026:46197"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:11.16.0-1.24.18.0.0.6.hum1"],"introduced":["0"],"last_affected":[],"package":"nodejs24-npm","purl":"pkg:rpm/redhat/nodejs24-npm","source":"RHSA-2026:46197"},{"ecosystem":"Red Hat:hummingbird:1","fixed":["0:24.18.0-0.6.hum1"],"introduced":["0"],"last_affected":[],"package":"nodejs24-npm-bin","purl":"pkg:rpm/redhat/nodejs24-npm-bin","source":"RHSA-2026:46197"}],"prev":{"headline":"Missing authorization in Rocket.Chat","id":"CVE-2026-48616"},"products":["node"],"published":"2026-06-18","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":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"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-18","vendors":["nodejs"]},"summary":"Attackers can bypass Node.js Permission Model restrictions via process.report.writeReport() path misvalidation, potentially accessing protected data.","url":"https://insights.sbomify.com/CVE-2026-48617/"}