LORIS has incorrect access checks in issue_tracker
Affects LORIS 16.0.0 through 28.0.1 with the issue_tracker module installed and enabled. Fixed in 27.0.4 and 28.0.2.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 27.0.4, 28.0.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
LORIS, a self-hosted web application used for data and project management in neuroimaging research, is affected by this vulnerability in its Issue Tracker module. An authenticated user could modify issues they are not permitted to edit, because the backend fails to properly check edit permissions even though the frontend restricts them.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
LORIS (Longitudinal Online Research and Imaging System) is a self-hosted web application that provides data- and project-management for neuroimaging research. In versions from 16.0.0 prior to 27.0.4 and from 28.0.0 prior to 28.0.2, the `issue_tracker` backend does not correctly verify edit access permissions, although the frontend restricts which issues a user may edit. An authenticated user can submit backend changes to issues outside the user's permitted edit scope. Deployments that no longer use Issue Tracker can disable the module to remove access to the endpoint. This issue is fixed in versions 27.0.4 and 28.0.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- aces Loris
From 16.0.0 · fixed in 27.0.4; From 28.0.0 · fixed in 28.0.2
References 5
Questions about CVE-2026-55146
What does this mean?
An authenticated user can change issues outside their permitted edit scope because the backend does not correctly verify edit access permissions.Source: github.com
Am I affected, and how do I check?
LORIS versions 16.0.0 through 28.0.1 are affected, but only where the issue_tracker module is installed and enabled. Check the installed LORIS version and whether issue_tracker is installed and enabled.Source: github.com
What should I do about it?
Upgrade to LORIS 27.0.4 or 28.0.2, depending on your release line. Projects that no longer use the Issue Tracker module can disable it to remove access to the endpoint.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data