chore(deps): update dependency hono to v4.9.7 [security] #35
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.9.6
->4.9.7
GitHub Vulnerability Alerts
CVE-2025-59139
Summary
A flaw in the
bodyLimit
middleware could allow bypassing the configured request body size limit when conflicting HTTP headers were present.Details
The middleware previously prioritized the
Content-Length
header even when aTransfer-Encoding: chunked
header was also included. According to the HTTP specification,Content-Length
must be ignored in such cases. This discrepancy could allow oversized request bodies to bypass the configured limit.Most standards-compliant runtimes and reverse proxies may reject such malformed requests with
400 Bad Request
, so the practical impact depends on the runtime and deployment environment.Impact
If body size limits are used as a safeguard against large or malicious requests, this flaw could allow attackers to send oversized request bodies. The primary risk is denial of service (DoS) due to excessive memory or CPU consumption when handling very large requests.
Resolution
The implementation has been updated to align with the HTTP specification, ensuring that
Transfer-Encoding
takes precedence overContent-Length
. The issue is fixed in Hono v4.9.7, and all users should upgrade immediately.Hono has Body Limit Middleware Bypass
CVE-2025-59139 / GHSA-92vj-g62v-jqhh
More information
Details
Summary
A flaw in the
bodyLimit
middleware could allow bypassing the configured request body size limit when conflicting HTTP headers were present.Details
The middleware previously prioritized the
Content-Length
header even when aTransfer-Encoding: chunked
header was also included. According to the HTTP specification,Content-Length
must be ignored in such cases. This discrepancy could allow oversized request bodies to bypass the configured limit.Most standards-compliant runtimes and reverse proxies may reject such malformed requests with
400 Bad Request
, so the practical impact depends on the runtime and deployment environment.Impact
If body size limits are used as a safeguard against large or malicious requests, this flaw could allow attackers to send oversized request bodies. The primary risk is denial of service (DoS) due to excessive memory or CPU consumption when handling very large requests.
Resolution
The implementation has been updated to align with the HTTP specification, ensuring that
Transfer-Encoding
takes precedence overContent-Length
. The issue is fixed in Hono v4.9.7, and all users should upgrade immediately.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
References
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
honojs/hono (hono)
v4.9.7
Compare Source
Security
bodyLimit
middleware where the body size limit could be bypassed when bothContent-Length
andTransfer-Encoding
headers were present. If you are using this middleware, please update immediately. Security AdvisoryWhat's Changed
parseResponse
not parsing json in react native by @lr0pb in #4399.tool-versions
file by @3w36zj6 in #4397bun install
commands to use--frozen-lockfile
by @3w36zj6 in #4398New Contributors
Full Changelog: honojs/hono@v4.9.6...v4.9.7
Configuration
📅 Schedule: Branch creation - "" in timezone Europe/Copenhagen, 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.
This PR was generated by Mend Renovate. View the repository job log.