fix(deps): update dependency @nestjs/core to ^11.1.18 [security]#852
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
fix(deps): update dependency @nestjs/core to ^11.1.18 [security]#852renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
Coverage Report for packages/configs/vitest-config
File CoverageNo changed files found. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^11.1.14→^11.1.18GitHub Vulnerability Alerts
CVE-2026-35515
Impact
What kind of vulnerability is it? Who is impacted?
SseStream._transform()interpolatesmessage.typeandmessage.iddirectly into Server-Sent Events text protocol output without sanitizing newline characters (\r,\n). Since the SSE protocol treats both\rand\nas field delimiters and\n\nas event boundaries, an attacker who can influence these fields through upstream data sources can inject arbitrary SSE events, spoof event types, and corrupt reconnection state. Spring Framework's own security patch (6e97587) validates these same fields (id,event) for the same reason.Actual impact:
event:types, causing client-sideEventSource.addEventListener()callbacks to fire for wrong event types.data:payloads, potentially triggering XSS if the client renders SSE data as HTML without sanitization.id:fields, corrupting theLast-Event-IDheader on reconnection, causing the client to miss or replay events.typeoridfields of SSE messages. Direct HTTP request input does not reach these fields without developer code bridging the gap.Patches
Has the problem been patched? What versions should users upgrade to?
Patched in
@nestjs/core@11.1.18Release Notes
nestjs/nest (@nestjs/core)
v11.1.18Compare Source
v11.1.18 (2026-04-03)
Bug fixes
microservicescoreDependencies
core,platform-express,platform-fastifyplatform-fastifyplatform-wscommonCommitters: 6
v11.1.17Compare Source
v11.1.17 (2026-03-16)
Enhancements
microservicesBugs
platform-fastifycbdf737(@kamilmysliwiec)Dependencies
commonplatform-fastifyCommitters: 3
v11.1.16Compare Source
v11.1.16 (2026-03-05)
Bug fixes
microservicesDependencies
platform-expressCommitters: 2
v11.1.15Compare Source
What's Changed
New Contributors
Full Changelog: nestjs/nest@v11.1.14...v11.1.15
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.