Hono: `csrf()` does not check requests sent by hyperlink auditing (`text/ping`)
Summary
csrf() validates a request only when its Content-Type is one of the three types an HTML form can send. Chromium's hyperlink auditing (<a ping>) sends a cross-origin POST with the user's cookies and the content type text/ping, which is not in that list. The middleware does not look at Origin or Sec-Fetch-Site for such a request, so it is passed to the handler.
Details
The middleware skips the origin check when the content type is not one that a form submission produces. The assumption was that any other content type requires a CORS preflight and therefore cannot be sent cross-origin with credentials. Hyperlink auditing is an exception: Chrome and Edge send the ping as a credentialed POST without a preflight, with a fixed body and Content-Type: text/ping.
A page on another origin can therefore trigger a POST to any URL of the application. The csrf() options for origin and secFetchSite do not change the outcome, because neither header is evaluated for the request.
The request body is fixed, so only actions whose effect does not depend on the body can be triggered. Firefox does not send pings by default. As with any CSRF, the user's cookie must be sent with the request, which with the default SameSite=Lax means a same-site origin or a cookie set with SameSite=None.
Impact
A user who visits a malicious page in Chrome or Edge while logged in to an application protected by csrf() can be made to send a state-changing request to that application, such as logging out, deleting a resource, or toggling a setting that is selected by the path or query string.
This issue affects applications that rely on csrf() as their CSRF protection and expose state-changing endpoints whose effect does not depend on the request body.
Workarounds
Reject requests with a Content-Type of text/ping in a middleware registered before csrf(), or set session cookies with SameSite=Strict.
Czego dotyczy
Kliknij technologię, aby zobaczyć wszystkie dotyczące jej podatności.
| Platforma | Paczka | Podatne wersje | Poprawka w wersji |
|---|---|---|---|
| Paczka npm | hono | < 4.13.16 | 4.13.16 |
Odnośniki
- Wektor CVSS
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N- Słabość (CWE)
CWE-352- Platforma
- npm
- Paczka
hono- Ujawniono
- 12.11.2026
- Aktualizacja
- 13.11.2026 01:17
Źródła i licencje
OSV / GitHub Advisory Database - GHSA-46wx-v44x-9hh2 - CC BY 4.0
Historia podatności: hono
Wszystkie opisane podatności tej paczki (Paczka npm), od najnowszej. Widać, czy to jednorazowa wpadka, czy paczka, której trzeba pilnować.
- Wszystkich wpisów
- 57
- Pierwsza → ostatnia
- 12.2023 11.2026
- Bez poprawki
- 0
- Wykorzystywana w atakach
- 0
Rozkład istotności
- Wysoka 7
- Średnia 45
- Niska 5
Ujawnienia w latach
- 2023: 1
- 2024: 3
- 2025: 4
- 2026: 49
-
Hono: `csrf()` does not check requests sent by hyperlink auditing (`text/ping`) ten wpis
Dowiedz się, które podatności dotyczą Twojej aplikacji
Po podłączeniu integracji DockRay i włączeniu raportowania oprogramowania DockRay porównuje zgłoszone wersje komponentów ze znanymi podatnościami i powiadamia o potwierdzonych dopasowaniach. Zakres zależy od obsługiwanej technologii i dostępnych biuletynów.