← Back
CVE-2026-81888
medium
CVSS 5.4
Cross-Site Request Forgery (CSRF) in @hono/oauth-providers (CVE-2026-81888)
Summary
vulnerability in @hono/oauth-providers (CVE-2026-81888). Risk of unauthorized operations or information disclosure. Exploitable via ``state``. Mitigation: upgrade to `0.8.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-81888** has been found in @hono/oauth-providers.
Attackers can target a specific entry point like ``state`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade @hono/oauth-providers to **0.8.6** or later.
If unsure, ask your IT team or search "@hono/oauth-providers CVE-2026-81888" on the vendor's site.
CVE-2026-81888 (@hono/oauth-providers) — CWE-352 / CVSS v3 5.4
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `state` / `GET` / `google` / `github`
Patched: `0.8.6` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**CSRF** (CWE-352) exists in @hono/oauth-providers. Attackers reach the vulnerable code path via ``state`` without authentication.
📍 Affected scope
@hono/oauth-providers — . Attack surface: `state` / `GET` / `google` / `github`.
🔥 Severity
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.8.6**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r '@hono/oauth-providers' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@hono/oauth-providers' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@hono/oauth-providers` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @hono/oauth-providers to 0.8.6ステージング環境で 0.8.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@hono/oauth-providers
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.8.6"}]}]
References
- web https://github.com/honojs/middleware/commit/b37765f40b7bddb1d8fce39573b085222dea58c1
- web https://github.com/honojs/middleware/pull/2040
- web https://github.com/honojs/middleware/releases/tag/%40hono%2Foauth-providers%400.8.6
- web https://github.com/honojs/middleware/security/advisories/GHSA-fm3f-ch8h-qw8q
- web https://github.com/advisories/GHSA-fm3f-ch8h-qw8q