github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 07:18:56 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #6703] [CLOSED] fix(deps): update dependency next to v16.0.10 [security] - autoclosed #6837

New Issue
Closed
opened 2026-03-13 13:13:22 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-13 13:13:22 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/6703
Author: @renovate[bot]
Created: 12/12/2025
Status: ❌ Closed

Base: canary ← Head: renovate/npm-next-vulnerability

📝 Commits (1)

  • 5ffad5e fix(deps): update dependency next to v16.0.10 [security]

📊 Changes

4 files changed (+76 additions, -86 deletions)

View changed files

📝 demo/nextjs/package.json (+1 -1)
📝 demo/stateless/package.json (+1 -1)
📝 docs/package.json (+1 -1)
📝 pnpm-lock.yaml (+73 -83)

📄 Description

This PR contains the following updates:

Package Change Age Confidence
next (source) 16.0.9 -> 16.0.10 age confidence

GitHub Vulnerability Alerts

GHSA-5j59-xgg2-r9c4

It was found that the fix addressing CVE-2025-55184 in React Server Components was incomplete and did not fully prevent denial-of-service attacks in all payload types. This affects React package versions 19.0.2, 19.1.3, and 19.2.2 and frameworks that use the affected packages, including Next.js 13.x, 14.x, 15.x and 16.x using the App Router. The issue is tracked upstream as CVE-2025-67779.

A malicious HTTP request can be crafted and sent to any Server Function endpoint that, when deserialized, can enter an infinite loop within the React Server Components runtime. This can cause the server process to hang and consume CPU, resulting in denial of service in unpatched environments.

Release Notes

vercel/next.js (next)

v16.0.10

Compare Source

Configuration

📅 Schedule: Branch creation - "" (UTC), 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 these updates again.

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

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

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/6703 **Author:** [@renovate[bot]](https://github.com/apps/renovate) **Created:** 12/12/2025 **Status:** ❌ Closed **Base:** `canary` ← **Head:** `renovate/npm-next-vulnerability` --- ### 📝 Commits (1) - [`5ffad5e`](https://github.com/better-auth/better-auth/commit/5ffad5e9cdb63538e9cd93e7a871421a143c2e98) fix(deps): update dependency next to v16.0.10 [security] ### 📊 Changes **4 files changed** (+76 additions, -86 deletions) <details> <summary>View changed files</summary> 📝 `demo/nextjs/package.json` (+1 -1) 📝 `demo/stateless/package.json` (+1 -1) 📝 `docs/package.json` (+1 -1) 📝 `pnpm-lock.yaml` (+73 -83) </details> ### 📄 Description This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [next](https://nextjs.org) ([source](https://redirect.github.com/vercel/next.js)) | [`16.0.9` -> `16.0.10`](https://renovatebot.com/diffs/npm/next/16.0.9/16.0.10) | ![age](https://developer.mend.io/api/mc/badges/age/npm/next/16.0.10?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/next/16.0.9/16.0.10?slim=true) | ### GitHub Vulnerability Alerts #### [GHSA-5j59-xgg2-r9c4](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-5j59-xgg2-r9c4) It was found that the fix addressing [CVE-2025-55184](https://redirect.github.com/advisories/GHSA-2m3v-v2m8-q956) in React Server Components was incomplete and did not fully prevent denial-of-service attacks in all payload types. This affects React package versions 19.0.2, 19.1.3, and 19.2.2 and frameworks that use the affected packages, including Next.js 13.x, 14.x, 15.x and 16.x using the App Router. The issue is tracked upstream as [CVE-2025-67779](https://www.cve.org/CVERecord?id=CVE-2025-67779). A malicious HTTP request can be crafted and sent to any Server Function endpoint that, when deserialized, can enter an infinite loop within the React Server Components runtime. This can cause the server process to hang and consume CPU, resulting in denial of service in unpatched environments. --- ### Release Notes <details> <summary>vercel/next.js (next)</summary> ### [`v16.0.10`](https://redirect.github.com/vercel/next.js/compare/v16.0.9...v16.0.10) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v16.0.9...v16.0.10) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "" (UTC), 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 these updates again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/better-auth/better-auth). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi40Mi4yIiwidXBkYXRlZEluVmVyIjoiNDIuNDIuMiIsInRhcmdldEJyYW5jaCI6ImNhbmFyeSIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=--> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-03-13 13:13:22 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#6837
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?