Skip to main content
VulnerabilityPublished Updated

CVE-2026-42259: saltcorn · Open Redirect

Affects saltcornSource GCVE Database

0

Not known to be exploited · CVSS 5.1 Medium · fixed in 1.6.0-beta.5 : update saltcorn when convenient.

Data as of 27 Oct 2026, 00:07 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.6.0-beta.5, 1.5.6, 1.4.6
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade saltcorn to 1.6.0-beta.5, 1.5.6 or 1.4.6.

Affected software

ProductAffectedFixed in
saltcorn saltcornAffected
  • <1.4.6
  • >=1.5.0-beta.0 <1.5.6
  • >=1.6.0-alpha.0 <1.6.0-beta.5
Fixed in
  • 1.4.6
  • 1.5.6
  • 1.6.0-beta.5

Description

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.

References

Community reviews

Loading reviews…