Skip to content
This repository was archived by the owner on Aug 15, 2026. It is now read-only.

chore(deps): update dependency @nestjs/core to v11.1.18 [security] - #172

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-nestjs-core-vulnerability
Open

chore(deps): update dependency @nestjs/core to v11.1.18 [security]#172
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/npm-nestjs-core-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Apr 7, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@nestjs/core (source) 11.1.1611.1.18 age confidence

@​nestjs/core Improperly Neutralizes Special Elements in Output Used by a Downstream Component ('Injection')

CVE-2026-35515 / GHSA-36xv-jgw5-4q75

More information

Details

Impact

What kind of vulnerability is it? Who is impacted?

SseStream._transform() interpolates message.type and message.id directly into Server-Sent Events text protocol output without sanitizing newline characters (\r, \n). Since the SSE protocol treats both \r and \n as field delimiters and \n\n as 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 spoofing: Attacker forges SSE events with arbitrary event: types, causing client-side EventSource.addEventListener() callbacks to fire for wrong event types.
  • Data injection: Attacker injects arbitrary data: payloads, potentially triggering XSS if the client renders SSE data as HTML without sanitization.
  • Reconnection corruption: Attacker injects id: fields, corrupting the Last-Event-ID header on reconnection, causing the client to miss or replay events.
  • Attack precondition: Requires the developer to map user-influenced data to the type or id fields 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.18

Severity

  • CVSS Score: 6.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:L/SA:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

nestjs/nest (@​nestjs/core)

v11.1.18

Compare Source

v11.1.18 (2026-04-03)
Bug fixes
Dependencies
Committers: 6

v11.1.17

Compare Source

v11.1.17 (2026-03-16)
Enhancements
Bugs
  • platform-fastify
    • auto-run middleware for HEAD requests as fastify redirects them to GET handlers (effectively skipping middleware execution) cbdf737 (@​kamilmysliwiec)
Dependencies
Committers: 3

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@vercel

vercel Bot commented Apr 7, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
marble-frontend Ignored Ignored Aug 14, 2026 9:00pm

@renovate
renovate Bot force-pushed the renovate/npm-nestjs-core-vulnerability branch from eb340ae to cc3ac09 Compare April 8, 2026 21:13
@renovate
renovate Bot force-pushed the renovate/npm-nestjs-core-vulnerability branch from cc3ac09 to b309cd1 Compare April 29, 2026 16:16
@renovate
renovate Bot force-pushed the renovate/npm-nestjs-core-vulnerability branch 2 times, most recently from 4108e71 to 3a29726 Compare May 18, 2026 09:59
@renovate
renovate Bot force-pushed the renovate/npm-nestjs-core-vulnerability branch from 3a29726 to ab64982 Compare May 28, 2026 17:42
@renovate
renovate Bot force-pushed the renovate/npm-nestjs-core-vulnerability branch 2 times, most recently from 4a947eb to 53bff3b Compare July 30, 2026 21:34
@renovate
renovate Bot force-pushed the renovate/npm-nestjs-core-vulnerability branch from 53bff3b to d5480a2 Compare August 12, 2026 01:10
@renovate
renovate Bot force-pushed the renovate/npm-nestjs-core-vulnerability branch from d5480a2 to 7ce112b Compare August 14, 2026 21:00
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants