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.
Original description
The description as published by the source.
Saltcorn is an extensible, open source, no-code database application builder. Prior to versions 1.4.6, 1.5.6, and 1.6.0-beta.5, Saltcorn validates the post-login dest parameter with a string check that only blocks :/ and //. Because all WHATWG-compliant browsers normalise backslashes () to forward slashes (/) for special schemes, a payload such as /\evil.com/path slips through is_relative_url(), is emitted unchanged in the HTTP Location header, and causes the browser to navigate cross-origin to an attacker-controlled domain. The bug is reachable on a default install and only requires a victim who can be tricked into logging in via a crafted Saltcorn URL. This issue has been patched in versions 1.4.6, 1.5.6, and 1.6.0-beta.5.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
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.
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.
A vulnerability (CWE-601) exists in @saltcorn/server. Attackers reach the vulnerable code path via dest.
Check the vendor advisory for the affected versions of @saltcorn/server. Attack surface: dest / Location / http / https.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.6.0-beta.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @saltcorn/server to 1.6.0-beta.5ステージング環境で 1.6.0-beta.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com