{"answers":{"affected":"2 open source packages ship an affected version, including @nestjs/core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-26108 in the wild and no public exploit code.","fix":"Upgrade @nestjs/core to 9.0.5 or later.","what":"CVE-2023-26108 is a low-severity vulnerability in @nestjs/core, published on 6 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-26108 and fix it if it is affected.\n\nWhat it is: CVE-2023-26108 is a low-severity vulnerability in @nestjs/core, published on 6 Mar 2023. 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-2023-26108 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @nestjs/core (npm): affected all versions; fixed in 9.0.5\n- @nestjs/core (npm): affected all versions; fixed in 9.0.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-2023-26108/ (Markdown: https://insights.sbomify.com/CVE-2023-26108/index.md)","id":"CVE-2023-26108","markdown":"https://insights.sbomify.com/CVE-2023-26108/index.md","name":"CVE-2023-26108","record":{"aliases":["GHSA-4jpv-8r57-pv7j"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"NestJS core library","requires_auth":"none","summary":"Attackers can keep file streams open by canceling requests, potentially leading to resource exhaustion or information exposure in NestJS applications.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"nest","vendor":"nestjs"}],"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-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Versions of the package @nestjs/core before 9.0.5 are vulnerable to Information Exposure via the StreamableFile pipe. Exploiting this vulnerability is possible when the client cancels a request while it is streaming a StreamableFile, the stream wrapped by the StreamableFile will be kept open.","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":"@nestjs/core vulnerable to Information Exposure via StreamableFile pipe","id":"CVE-2023-26108","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":2,"n_references":4,"next":{"headline":"node-bluetooth-serial-port is vulnerable to Buffer Overflow via the findSerialPortChannel","id":"CVE-2023-26109"},"packages":[{"ecosystem":"npm","fixed":["9.0.5"],"introduced":["0"],"last_affected":[],"package":"@nestjs/core","purl":null,"source":"GHSA-4jpv-8r57-pv7j"},{"ecosystem":"npm","fixed":["9.0.5"],"introduced":["0"],"last_affected":[],"package":"@nestjs/core","purl":"pkg:npm/%40nestjs/core","source":"GHSA-4jpv-8r57-pv7j"}],"prev":{"headline":"SketchSVG Arbitrary Code Injection vulnerability","id":"CVE-2023-26107"},"products":["@nestjs/core"],"published":"2023-03-06","related":[{"cvss_score":8.7,"headline":"Nest Fastify HEAD Request Middleware Bypass","id":"CVE-2026-33011","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":8.2,"headline":"NestJS 11.1.13 - Lack of data validation allowing authentication/authorization bypass","id":"CVE-2026-2293","kev_date_added":null,"published":"2026-02-27"},{"cvss_score":7.5,"headline":"Nest: DoS via Recursive handleData in JsonSocket (TCP Transport)","id":"CVE-2026-40879","kev_date_added":null,"published":"2026-04-21"},{"cvss_score":6.9,"headline":"Nest has a Fastify URL Encoding Middleware Bypass (TOCTOU)","id":"CVE-2025-69211","kev_date_added":null,"published":"2025-12-29"},{"cvss_score":6.3,"headline":"@nestjs/core Improperly Neutralizes Special Elements in Output Used by a Downstream Component ('Injection')","id":"CVE-2026-35515","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":5.5,"headline":"nest allows a remote attacker to execute arbitrary code via the Content-Type header","id":"CVE-2024-29409","kev_date_added":null,"published":"2025-03-14"}],"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":"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":"2025-03-05","vendors":["n/a"]},"summary":"Attackers can keep file streams open by canceling requests, potentially leading to resource exhaustion or information exposure in NestJS applications.","url":"https://insights.sbomify.com/CVE-2023-26108/"}