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