← Back
CVE-2026-42565
medium
CVSS 4.3
Open Redirect in @workos/authkit-session (CVE-2026-42565)
Summary
vulnerability in @workos/authkit-session (CVE-2026-42565). Risk of unauthorized operations or information disclosure. Exploitable via ``AuthService.handleCallback``. Mitigation: upgrade to `0.5.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42565** has been found in @workos/authkit-session.
Attackers can target a specific entry point like ``AuthService.handleCallback`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade @workos/authkit-session to **0.5.1** or later.
If unsure, ask your IT team or search "@workos/authkit-session CVE-2026-42565" on the vendor's site.
CVE-2026-42565 (@workos/authkit-session) — CWE-601 / CVSS v3 4.3
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `AuthService.handleCallback` / `returnPathname` / `state` / `Location`
Patched: `0.5.1` — 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
**A vulnerability** (CWE-601) exists in @workos/authkit-session. Attackers reach the vulnerable code path via ``AuthService.handleCallback`` without authentication.
📍 Affected scope
@workos/authkit-session — . Attack surface: `AuthService.handleCallback` / `returnPathname` / `state` / `Location`.
🔥 Severity
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.5.1**.
🛡️ 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 '@workos/authkit-session' .` 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 '@workos/authkit-session' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `@workos/authkit-session` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade @workos/authkit-session to 0.5.1ステージング環境で 0.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@workos/authkit-session
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.5.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-42565
- package https://github.com/workos/authkit-session
- web https://github.com/workos/authkit-session/commit/f56e1d6214a93160759e5677b7a3d772b244db39
- web https://github.com/workos/authkit-session/releases/tag/v0.5.1
- web https://github.com/workos/authkit-session/security/advisories/GHSA-vvvv-983w-r7pv
- web https://github.com/advisories/GHSA-vvvv-983w-r7pv