VulnerabilityPublished 8 Apr 2026

CVE-2026-35400: aces Loris · Link Following

Affects aces LorisSource CVE Database V5

Compare

Not known to be exploited · CVSS 3.5 Low : upgrade to 28.0.1 or 27.0.3 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

3.5Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 28.0.1, 27.0.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade aces Loris to 28.0.1 or 27.0.3.

Affected software

Product	Affected	Fixed in
acesLoris	Affected >=28.0.0 <28.0.1	Fixed in 28.0.1
acesLoris	Affected >=20.0.0 <27.0.3	Fixed in 27.0.3

AI-suggested

A fix is available in LORIS versions 27.0.3 and 28.0.1. Users should upgrade to these or later versions to remediate the vulnerability. Since this is a self-hosted application, administrators must apply the update manually. Patch status is confirmed by the vendor's versioning information. No additional mitigation steps are specified.

Description

LORIS (Longitudinal Online Research and Imaging System) is a self-hosted web application that provides data- and project-management for neuroimaging research. From 20.0.0 to before 27.0.3 and 28.0.1, an endpoint in the publication module was incorrectly trusting the baseURL submitted by a user's POST request rather than the internal LORIS value. This could result in a theoretical attacker with publication module access forging an email to an external domain under the attacker's control which appeared to come from LORIS. This vulnerability is fixed in 27.0.3 and 28.0.1.

Impact

The vulnerability allows an attacker with publication module access to send forged emails that appear to come from the LORIS system to external domains. There is no impact on confidentiality or availability. The integrity impact is low, as the attacker can only manipulate the sender address in emails. No known exploits are reported in the wild.

Summary

The LORIS application improperly trusts the baseURL submitted by a user's POST request in the publication module, rather than using the internal LORIS value. This flaw allows a user with access to the publication module to forge emails to external domains that appear to originate from LORIS. The vulnerability affects versions from 20.0.0 up to but not including 27.0.3, and from 28.0.0 up to but not including 28.0.1. The issue is addressed in versions 27.0.3 and 28.0.1. The CVSS 3.1 base score is 3.5, indicating low severity, with network attack vector, low attack complexity, requiring low privileges and user interaction, and impacts limited to integrity only.

CWE-59Improper Link Resolution Before File Access (Link Following) (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
Architecture and Design · Separation of Privilege
Follow the principle of least privilege when assigning access rights to entities in a software system.
OWASP Cheat Sheets
Authorization (opens in a new tab)
Attack patterns
Symlink Attack (opens in a new tab)
Using Malicious Files (opens in a new tab)
Leverage Executable Code in Non-Executable Files (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/aces/Loris/security/advisories/GHSA-6prw-34x8-3gpg (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Apr 2026, 20:20 UTC

WeaknessesCWE-59

Technical details

References

Community reviews

Related threats