CVE-2026-35165: aces Loris · Insecure Direct Object Reference
Affects aces LorisSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 28.0.1 or 27.0.3 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% 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:N/S:U/C:L/I:L/A:LExploitation 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 30 Oct 2026.
What to do
Upgrade Loris to 28.0.1 or 27.0.3; aces/Loris to 27.0.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| acesLoris | Affected
| Fixed in
|
| acesLoris | Affected
| Fixed in
|
GitHubaces/Lorispkg:github/aces/LorisOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade affected LORIS instances to version 27.0.3 or later, or 28.0.1 or later, where this authorization bypass vulnerability is fixed. Since this is a self-hosted application, administrators must apply these updates manually. Patch status is confirmed fixed in these versions. No vendor advisory was provided to indicate alternative mitigations or temporary fixes.
Description
LORIS (Longitudinal Online Research and Imaging System) is a self-hosted web application that provides data- and project-management for neuroimaging research. From 21.0.0 to before 27.0.3 and 28.0.1, while the document_repository frontend was restricting file access, the backend endpoint was not correctly verifying access permissions. A user could theoretically download a file that they should not have access to, if they know or can brute force the filename. This vulnerability is fixed in 27.0.3 and 28.0.1.