Skip to content

chore(deps): bump the npm-security group across 1 directory with 2 updates - #37

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/src/ShutterSpool.Web/npm-security-89d5621eb3
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/src/ShutterSpool.Web/npm-security-89d5621eb3

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the npm-security group with 2 updates in the /src/ShutterSpool.Web directory: @nuxt/nitro-server and node-forge.

Updates @nuxt/nitro-server from 4.6.2 to 4.6.4

Release notes

Sourced from @​nuxt/nitro-server's releases.

v4.6.4

4.6.4 is a security release. It fixes eight advisories in Nuxt and pulls in nitropack 2.13.6, which fixes three more in Nitro. We recommend upgrading as soon as you can.

⚠️ Behaviour changes

These probably won't affect most apps, but it's worth flagging anyway:

  1. Error details in production. When a page fails to render on the server, the error page and the payload now only carry message and data of errors you create with createError. Everything else is stripped.
  2. Dev server Host checks. Webpack and rspack dev servers now reject requests with an unexpected Host header, as Vite already does. If you use a custom hostname or tunnel, you'll need to add it to the new devServer.allowedHosts option.
  3. workspaceDir detection. When workspaceDir isn't set, Nuxt now only widens it past rootDir to an explicit workspace root or the closest git repository.
  4. Nitropack cached routes. cache, swr and isr route rules now only cache GET and HEAD requests, and no longer store responses that set a cookie or send Cache-Control: private or no-store. Wildcard proxy and redirect rules also reject requests whose resolved target would leave the rule's scope.
  5. Route rules and encoded slashes. Route rules now match paths that contain encoded slashes, so /api%2Fadmin is covered by a /api/** rule.

👉 Changelog

compare changes

🩹 Fixes

  • nitro,nuxt: require unrouting 0.3.2 (768d21368)
  • nitro: preserve wildcard tails in case-insensitive route rules (bf31e4cd8)
  • nitro: require nitropack 2.13.6 (1b13c6981)
  • nitro: keep leading double slash in renderer request path (75c12c6fb)
  • nuxt: use unambiguous encoding for island hash (6f1b93c64)
  • vite-server: resolve wildcard redirect tails from the matched segments (1e7dfa6a7)
  • nuxt: do not expose details of untrusted thrown errors (8c56b71e4)
  • nuxt: strip trailing slashes in linear time (97424dd21)
  • nitro,webpack: include hosts the CLI allows after loading the config (8c11d965d)
  • webpack: skip hot middleware for forbidden dev requests (3c9645326)
  • rspack,webpack: reject unexpected Host headers in dev middleware (f8d64c9aa)
  • schema,nitro,vite: add devServer.allowedHosts (3e1c7964e)
  • nitro,nuxt: match route rules for paths with encoded slashes (084396b10)
  • schema: only widen workspace dir to a declared workspace root (89d3306d1)
  • nitro: only trust x-forwarded-proto in when opted-in (#36818)
  • nitro: stream the body read through a nuxt/server handler (#36817)
  • kit: suggest the specific fix when loading falls back to jiti (24d75659d)
  • vite: use a single type checker (#36774)
  • nitro,vite: remove windows + virtual dev ssr css links after hydration (#36765)
  • nitro,vite: dedupe dev css by module node (#36420)
  • nuxt: avoid hoisting setup-only values from definePageMeta (#36751)
  • nuxt: only match hydration modifiers after lazy prefix (#36750)
  • kit,nitro,nuxt: make emitted tsconfig/types stable across reruns (#36747)
  • nuxt: render inlined component styles after stylesheet links (#36714)
  • webpack: use valid devtool for hidden client sourcemaps in dev (#36555)

📖 Documentation

  • clarify template dependency regeneration (#36766)
  • revise README structure and headings (#36772)
  • link the Nuxt DevTools docs on nuxt.com (#36769)

... (truncated)

Commits
  • b9a6b68 v4.6.4 (#36823)
  • bf31e4c fix(nitro): preserve wildcard tails in case-insensitive route rules
  • 1b13c69 fix(nitro): require nitropack 2.13.6
  • 75c12c6 fix(nitro): keep leading double slash in renderer request path
  • 8c11d96 fix(nitro,webpack): include hosts the CLI allows after loading the config
  • 3e1c796 fix(schema,nitro,vite): add devServer.allowedHosts
  • 084396b fix(nitro,nuxt): match route rules for paths with encoded slashes
  • 19cf105 fix(nitro): only trust x-forwarded-proto in when opted-in (#36818)
  • 60c6952 fix(nitro): stream the body read through a nuxt/server handler (#36817)
  • 40f72b4 test: tolerate node 26 proxy inspect output
  • Additional commits viewable in compare view

Updates node-forge from 1.4.0 to 1.4.3

Changelog

Sourced from node-forge's changelog.

1.4.3 - 2026-11-03

Security

  • HIGH: X.509 certificate chain verification ignores name constraints.
    • pki.verifyCertificateChain() does not check the nameConstraints extension (RFC 5280 4.2.1.10). A non-critical nameConstraints extension in a CA certificate is ignored, so a name-constrained intermediate CA can issue certificates for names outside its permitted subtrees, or inside its excluded subtrees, and the chain verifies. Exploitation requires the private key of a name-constrained CA that chains to a trusted root. A critical nameConstraints extension is rejected as an unsupported critical extension.
    • Reported by @​bhaswanthc.
    • CVE ID: CVE-TBD
    • GHSA ID: GHSA-3cc4-3294-vgjf
  • MODERATE: TLS client crash on a handshake record without a session.
    • A TLS client throws an uncaught TypeError from process() when it receives a ServerHello while it has no session: after a close_notify alert or a call to close(), or before handshake() is called. A malicious server, or an on-path attacker, can terminate a Node.js process that passes socket data to process() without catching exceptions. Servers are not affected.
    • Reported by @​manus-use.
    • CVE ID: CVE-TBD
    • GHSA ID: GHSA-j8rw-jp99-435v
  • MODERATE: ReDoS in forge.http response header parsing.
    • forge.http trims response header and Set-Cookie values with a regular expression that takes quadratic time on a long run of whitespace followed by another character. A server, or an on-path attacker, can block a forge.http client for minutes with one large header.
    • Reported by @​manus-pi.
    • CVE ID: CVE-TBD
    • GHSA ID: GHSA-6cv4-p8m7-4r25
  • MODERATE: TLS client crash on an unsupported ServerHello compression method.
    • A TLS client accepts any compression method in the ServerHello, although it only offers no compression. An unknown method makes process() throw an uncaught Error at ServerHelloDone, before the server is authenticated. A malicious server, or an on-path attacker, can terminate a Node.js process that passes socket data to process() without catching exceptions, including through forge.tls.wrapSocket. Servers are not affected.
    • Reported by @​alienkeric.
    • CVE ID: CVE-TBD
    • GHSA ID: GHSA-w4xr-hqv8-ch44
  • LOW: Ed25519 signature verification accepts small-order public keys.
    • ed25519.verify() does not reject public keys of small order, such as the identity point. Under such a key, a signature with S = 0 and a small-order R verifies for many or, with the identity key, all messages, without any private key. Applications are affected only if

... (truncated)

Commits
  • 936b24d Release 1.4.3.
  • 4d8f79a Update changelog.
  • 1d9816d Check the ServerHello compression method.
  • 326a4d0 Trim forge.http header values in linear time.
  • 2cfaeb5 Ignore handshake messages on a TLS client without a session.
  • 6b23eae Complete nameConstraints enforcement.
  • 862aa5f Enforce nameConstraints in verifyCertificateChain().
  • 956f2b5 Document ed25519.verify() small-order key behavior.
  • 1b77e6f Reject small-order Ed25519 public keys in verify.
  • 2bd5146 Add GitHub usernames to credits.
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 13, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/src/ShutterSpool.Web/npm-security-89d5621eb3 branch 2 times, most recently from 1d0398c to 36ecda0 Compare November 15, 2026 08:06
…dates

Bumps the npm-security group with 2 updates in the /src/ShutterSpool.Web directory: [@nuxt/nitro-server](https://github.com/nuxt/nuxt/tree/HEAD/packages/nitro-server) and [node-forge](https://github.com/digitalbazaar/forge).


Updates `@nuxt/nitro-server` from 4.6.2 to 4.6.4
- [Release notes](https://github.com/nuxt/nuxt/releases)
- [Commits](https://github.com/nuxt/nuxt/commits/v4.6.4/packages/nitro-server)

Updates `node-forge` from 1.4.0 to 1.4.3
- [Changelog](https://github.com/digitalbazaar/forge/blob/main/CHANGELOG.md)
- [Commits](digitalbazaar/forge@v1.4.0...v1.4.3)

---
updated-dependencies:
- dependency-name: "@nuxt/nitro-server"
  dependency-version: 4.6.4
  dependency-type: indirect
  dependency-group: npm-security
- dependency-name: node-forge
  dependency-version: 1.4.3
  dependency-type: indirect
  dependency-group: npm-security
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/src/ShutterSpool.Web/npm-security-89d5621eb3 branch from 36ecda0 to 13aa313 Compare November 15, 2026 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants