Skip to content

fix(deps): Update dependency next to v15.5.14 [SECURITY] - abandoned - #8

Closed
cq-bot wants to merge 1 commit into
masterfrom
renovate/npm-next-vulnerability
Closed

fix(deps): Update dependency next to v15.5.14 [SECURITY] - abandoned#8
cq-bot wants to merge 1 commit into
masterfrom
renovate/npm-next-vulnerability

Conversation

@cq-bot

@cq-bot cq-bot commented Mar 22, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
next (source) 15.5.1215.5.14 age confidence

GitHub Vulnerability Alerts

CVE-2026-29057

Summary

When Next.js rewrites proxy traffic to an external backend, a crafted DELETE/OPTIONS request using Transfer-Encoding: chunked could trigger request boundary disagreement between the proxy and backend. This could allow request smuggling through rewritten routes.

Impact

An attacker could smuggle a second request to unintended backend routes (for example, internal/admin endpoints), bypassing assumptions that only the configured rewrite destination/path is reachable. This does not impact applications hosted on providers that handle rewrites at the CDN level, such as Vercel.

Patches

The vulnerability originated in an upstream library vendored by Next.js. It is fixed by updating that dependency’s behavior so content-length: 0 is added only when both content-length and transfer-encoding are absent, and transfer-encoding is no longer removed in that code path.

Workarounds

If upgrade is not immediately possible:

  • Block chunked DELETE/OPTIONS requests on rewritten routes at your edge/proxy.
  • Enforce authentication/authorization on backend routes per our security guidance.

CVE-2026-27980

Summary

The default Next.js image optimization disk cache (/_next/image) did not have a configurable upper bound, allowing unbounded cache growth.

Impact

An attacker could generate many unique image-optimization variants and exhaust disk space, causing denial of service. Note that this does not impact platforms that have their own image optimization capabilities, such as Vercel.

Patches

Fixed by adding an LRU-backed disk cache with images.maximumDiskCacheSize, including eviction of least-recently-used entries when the limit is exceeded. Setting maximumDiskCacheSize: 0 disables disk caching.

Workarounds

If upgrade is not immediately possible:

  • Periodically clean .next/cache/images.
  • Reduce variant cardinality (e.g., tighten values for images.localPatterns, images.remotePatterns, and images.qualities)

Release Notes

vercel/next.js (next)

v15.5.14

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes
  • feat(next/image): add lru disk cache and images.maximumDiskCacheSize (#​91660)
  • Fix(pages-router): restore Content-Length and ETag for /_next/data/ JSON responses (#​90304)
Credits

Huge thanks to @​styfle and @​lllomh for helping!

v15.5.13

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes
  • fix: patch http-proxy to prevent request smuggling in rewrites (See: CVE-2026-29057)
Credits

Huge thanks to @​ztanner for helping!


Configuration

📅 Schedule: 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 has been generated by Renovate Bot.

@cq-bot cq-bot added automerge Add to automerge PRs once requirements are met security labels Mar 22, 2026
@cq-bot cq-bot changed the title fix(deps): Update dependency next to v15.5.13 [SECURITY] fix(deps): Update dependency next to v15.5.13 [SECURITY] - autoclosed Mar 22, 2026
@cq-bot cq-bot closed this Mar 22, 2026
@cq-bot
cq-bot deleted the renovate/npm-next-vulnerability branch March 22, 2026 03:21
@cq-bot cq-bot changed the title fix(deps): Update dependency next to v15.5.13 [SECURITY] - autoclosed fix(deps): Update dependency next to v15.5.14 [SECURITY] Mar 23, 2026
@cq-bot cq-bot reopened this Mar 23, 2026
@cq-bot
cq-bot force-pushed the renovate/npm-next-vulnerability branch from b10f001 to ecfedce Compare March 23, 2026 16:51
@cq-bot cq-bot changed the title fix(deps): Update dependency next to v15.5.14 [SECURITY] fix(deps): Update dependency next to v15.5.14 [SECURITY] - autoclosed Mar 23, 2026
@cq-bot cq-bot closed this Mar 23, 2026
@cq-bot cq-bot changed the title fix(deps): Update dependency next to v15.5.14 [SECURITY] - autoclosed fix(deps): Update dependency next to v15.5.14 [SECURITY] Mar 26, 2026
@cq-bot cq-bot reopened this Mar 26, 2026
@cq-bot
cq-bot force-pushed the renovate/npm-next-vulnerability branch 2 times, most recently from ecfedce to 74d0e3b Compare March 26, 2026 17:10
@cloudquery-ci cloudquery-ci Bot changed the title fix(deps): Update dependency next to v15.5.14 [SECURITY] fix(deps): Update dependency next to v15.5.14 [SECURITY] - abandoned Mar 26, 2026
@cloudquery-ci

cloudquery-ci Bot commented Mar 26, 2026

Copy link
Copy Markdown

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge Add to automerge PRs once requirements are met security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants