# CVE-2026-47675: Hono: Cookie helper does not sanitize sameSite and priority, allowing Set-Cookie injection

> Attackers can inject arbitrary attributes into Set-Cookie headers via unsanitized sameSite and priority options in the Hono framework.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 28 May 2026
- **Also known as:** ECHO-d26c-09d1-ea7b, GHSA-3hrh-pfw6-9m5x, MINI-39pr-rf8h-4p88, MINI-8j4f-66v7-mqxc, MINI-9fvr-cr74-rh67, MINI-c524-9r7g-x6g6, MINI-c6c4-8r59-2gvg, MINI-f6r3-rwrv-xpcx, MINI-gh76-56rx-f3ww, MINI-jvgm-qfx5-jhh8, MINI-q7c6-w75x-hpqm, MINI-vwx9-3fp6-m662, MINI-xqhq-fh3w-768g, ROOT-APP-NPM-CVE-2026-47675

## What is CVE-2026-47675?

CVE-2026-47675 is a medium-severity vulnerability in honojs hono, published on 28 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.21, the serialize() function in hono/cookie validates domain and path options against characters that corrupt Set-Cookie header syntax (;, \r, \n), but does not apply the same validation to sameSite and priority. An application that passes user-controlled input into either option may produce a Set-Cookie response header containing attacker-chosen additional attributes. This vulnerability is fixed in 4.12.21.

Weakness: CWE-1287 (Improper Validation of Specified Type of Input), CWE-113 (Improper Neutralization of CRLF Sequences in HTTP Headers)

## Which versions are affected by CVE-2026-47675?

2 open source packages ship an affected version, including hono. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `hono` | npm | All versions | 4.12.21 |
| `hono` | npm | All versions | 4.12.21 |

Products: Hono Hono.

## How do I fix CVE-2026-47675?

Upgrade hono to 4.12.21 or later.

## Is CVE-2026-47675 being exploited?

There is no known exploitation of CVE-2026-47675 in the wild and no public exploit code.

## Other vulnerabilities in honojs hono

- [CVE-2026-27700](https://insights.sbomify.com/CVE-2026-27700/): Hono is Vulnerable to Authentication Bypass by IP Spoofing in AWS Lambda ALB conninfo (high 8.2)
- [CVE-2026-22817](https://insights.sbomify.com/CVE-2026-22817/): JWT Algorithm Confusion via Unsafe Default (HS256) in Hono JWT Middleware Allows Token Forgery and Auth Bypass (high 8.2)
- [CVE-2026-22818](https://insights.sbomify.com/CVE-2026-22818/): JWT algorithm confusion in Hono JWK Auth Middleware when JWK lacks "alg" (untrusted header.alg fallback) (high 8.2)
- [CVE-2025-62610](https://insights.sbomify.com/CVE-2025-62610/): Hono Improperly Authorizes JWT Audience Validation (high 8.1)
- [CVE-2026-29045](https://insights.sbomify.com/CVE-2026-29045/): Hono: Arbitrary file access via serveStatic vulnerability (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47675 and fix it if it is affected.

What it is: CVE-2026-47675 is a medium-severity vulnerability in honojs hono, published on 28 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-47675 in the wild and no public exploit code.

Affected packages and fixed versions:
- hono (npm): affected all versions; fixed in 4.12.21
- hono (npm): affected all versions; fixed in 4.12.21

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47675/ (Markdown: https://insights.sbomify.com/CVE-2026-47675/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47675
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47675
- OSV: https://osv.dev/vulnerability/CVE-2026-47675

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47675/
Summaries are generated and may contain mistakes; the official description above is the record.