7 matches found
CVE-2026-35515
NestJS/core (@nestjs/core) contains a vulnerability in SseStream._transform() where un sanitized interpolation of upstream data into SSE output allows an attacker to inject arbitrary SSE events, spoof event types, and corrupt reconnection state. The issue arises from inserting message.type and me...
CVE-2024-29409
CVE-2024-29409 : The IBM NOI bulletin confirms a file-upload vulnerability in NestJS Nest v10.3.2 where arbitrary code execution is possible via the Content-Type header, i.e., a remote attacker can exploit a crafted upload request that abuses Content-Type handling. The document does not provide r...
CVE-2023-26108
CVE-2023-26108 affects the NestJS framework component @nestjs/core when running versions prior to 9.0.5 . The vulnerability enables information exposure via the StreamableFile pipe if a client cancels a request while streaming; the underlying stream remains open, potentially leaking data. Connect...
CVE-2026-2293
Summary: CVE-2026-2293 describes a bypass of authentication/authorization in NestJS apps using @nestjs/platform-fastify when Fastify path-normalization options are enabled. The root cause is a mismatch between middleware evaluation and route dispatch due to differing URL interpretations, allowing...
CVE-2026-33011
CVE-2026-33011 affects Nest with @nestjs/platform-fastify: in versions 11.1.15 and earlier, Fastify’s HEAD-to-GET redirect can bypass GET middleware, causing middleware to be skipped while the GET handler still runs and the response lacks a body. The issue is fixed in version 11.1.16. Remediate b...
CVE-2025-69211
CVE-2025-69211 affects Nest.js applications using the Fastify platform integration before version 11.1.11. The issue is a bypass in the Fastify URL encoding middleware that can skip security checks implemented via NestMiddleware (via MiddlewareConsumer) or app.use(), particularly when middleware ...
CVE-2026-40879
Summary: Nest (Node.js) suffers a DoS via recursive handling of JSON frames over TCP. Before 11.1.19, handleData() recursed for each valid JSON message in a single frame, causing call stack growth and eventual RangeError when a ~47 KB payload is sent. This is fixed in 11.1.19. What’s affected: Th...