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

[PR #5558] [CLOSED] chore(deps): update dependency hono to v4.10.3 [security] #6083

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

📋 Pull Request Information

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

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

📝 Commits (1)

  • 1ba8d7d chore(deps): update dependency hono to v4.10.3 [security]

📊 Changes

1 file changed (+77 additions, -631 deletions)

View changed files

📝 pnpm-lock.yaml (+77 -631)

📄 Description

This PR contains the following updates:

Package Change Age Confidence
hono (source) 4.10.2 -> 4.10.3 age confidence

GitHub Vulnerability Alerts

GHSA-q7jf-gf43-6x6p

Summary

A flaw in the CORS middleware allowed request Vary headers to be reflected into the response, enabling attacker-controlled Vary values and potentially affecting cache behavior.

Details

The middleware previously copied the Vary header from the request when origin was not set to "*". Since Vary is a response header that should only be managed by the server, this could allow an attacker to influence caching behavior or cause inconsistent CORS handling.

Most environments will see impact only when shared caches or proxies rely on the Vary header. The practical effect varies by configuration.

Impact

May cause cache key pollution and inconsistent CORS enforcement in certain setups. No direct confidentiality, integrity, or availability impact in default configurations.

Resolution

Update to the latest patched release. The CORS middleware has been corrected to handle Vary exclusively as a response header.

Release Notes

honojs/hono (hono)

v4.10.3

Compare Source

Securiy Fix

A security issue in the CORS middleware has been fixed. In some cases, a request header could affect the Vary response header. Please update to the latest version if you are using the CORS middleware.

What's Changed

New Contributors

Full Changelog: https://github.com/honojs/hono/compare/v4.10.2...v4.10.3

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/5558 **Author:** [@renovate[bot]](https://github.com/apps/renovate) **Created:** 10/24/2025 **Status:** ❌ Closed **Base:** `canary` ← **Head:** `renovate/npm-hono-vulnerability` --- ### 📝 Commits (1) - [`1ba8d7d`](https://github.com/better-auth/better-auth/commit/1ba8d7db6bbfb7b1446c442d4c3a6ac0d8ba41ec) chore(deps): update dependency hono to v4.10.3 [security] ### 📊 Changes **1 file changed** (+77 additions, -631 deletions) <details> <summary>View changed files</summary> 📝 `pnpm-lock.yaml` (+77 -631) </details> ### 📄 Description This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [hono](https://hono.dev) ([source](https://redirect.github.com/honojs/hono)) | [`4.10.2` -> `4.10.3`](https://renovatebot.com/diffs/npm/hono/4.10.2/4.10.3) | [![age](https://developer.mend.io/api/mc/badges/age/npm/hono/4.10.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/hono/4.10.2/4.10.3?slim=true)](https://docs.renovatebot.com/merge-confidence/) | ### GitHub Vulnerability Alerts #### [GHSA-q7jf-gf43-6x6p](https://redirect.github.com/honojs/hono/security/advisories/GHSA-q7jf-gf43-6x6p) ### Summary A flaw in the CORS middleware allowed request `Vary` headers to be reflected into the response, enabling attacker-controlled `Vary` values and potentially affecting cache behavior. ### Details The middleware previously copied the `Vary` header from the request when `origin` was not set to `"*"`. Since `Vary` is a response header that should only be managed by the server, this could allow an attacker to influence caching behavior or cause inconsistent CORS handling. Most environments will see impact only when shared caches or proxies rely on the `Vary` header. The practical effect varies by configuration. ### Impact May cause cache key pollution and inconsistent CORS enforcement in certain setups. No direct confidentiality, integrity, or availability impact in default configurations. ### Resolution Update to the latest patched release. The CORS middleware has been corrected to handle `Vary` exclusively as a response header. --- ### Release Notes <details> <summary>honojs/hono (hono)</summary> ### [`v4.10.3`](https://redirect.github.com/honojs/hono/releases/tag/v4.10.3) [Compare Source](https://redirect.github.com/honojs/hono/compare/v4.10.2...v4.10.3) #### Securiy Fix A security issue in the CORS middleware has been fixed. In some cases, a request header could affect the Vary response header. Please update to the latest version if you are using the CORS middleware. #### What's Changed - fix(aws-lambda): serve microsoft office files as binary in lambda handler by [@&#8203;matthiasfeist](https://redirect.github.com/matthiasfeist) in [#&#8203;4469](https://redirect.github.com/honojs/hono/pull/4469) - fix(request-id): validation accepts `=` by [@&#8203;ryuapp](https://redirect.github.com/ryuapp) in [#&#8203;4478](https://redirect.github.com/honojs/hono/pull/4478) - refactor(jwt): reduce the size of the code generated by minification by [@&#8203;usualoma](https://redirect.github.com/usualoma) in [#&#8203;4480](https://redirect.github.com/honojs/hono/pull/4480) #### New Contributors - [@&#8203;matthiasfeist](https://redirect.github.com/matthiasfeist) made their first contribution in [#&#8203;4469](https://redirect.github.com/honojs/hono/pull/4469) **Full Changelog**: <https://github.com/honojs/hono/compare/v4.10.2...v4.10.3> </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:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNTYuMSIsInVwZGF0ZWRJblZlciI6IjQxLjE1Ni4xIiwidGFyZ2V0QnJhbmNoIjoiY2FuYXJ5IiwibGFiZWxzIjpbImRlcGVuZGVuY2llcyJdfQ==--> --- <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 12:46:57 -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#6083
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?