VulnerabilityPublished 30 Oct 2026

CVE-2026-55146: aces Loris · Missing Authorization

Affects aces LorisSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 28.0.2 or 27.0.4 when convenient.

Data as of 30 Oct 2026, 21:52 UTC

CVSS 3.1 base score

4.3Medium

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

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	4.3

Patch: Available – fixed in 28.0.2, 27.0.4

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
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: None: The vulnerable system can be exploited without any interaction from any user.
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 30 Oct 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.

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 Loris and aces/Loris to 28.0.2 or 27.0.4.

Affected software

Product	Affected	Fixed in
acesLoris	Affected >=28.0.0 <28.0.2	Fixed in 28.0.2
acesLoris	Affected >=16.0.0 <27.0.4	Fixed in 27.0.4
GitHubaces/Loris`pkg:github/aces/Loris`Other threats	Affected >=16.0.0 <27.0.4 >=28.0.0 <28.0.2	Fixed in 27.0.4 28.0.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade LORIS to version 27.0.4 or later in the 27.x series, or to version 28.0.2 or later in the 28.x series to apply the official fix. If the Issue Tracker module is not used, disable it to remove access to the vulnerable backend endpoint. No other specific mitigations are indicated.

Description

LORIS is a neuroimaging research management web application with a vulnerability in its issue_tracker backend. Versions from 16.0.0 prior to 27.0.4 and from 28.0.0 prior to 28.0.2 do not properly verify edit access permissions on the backend, allowing authenticated users to modify issues beyond their allowed scope. The frontend restricts issue editing, but the backend flaw bypasses these controls. The issue is fixed in versions 27.0.4 and 28.0.2. Deployments not using the Issue Tracker module can disable it to mitigate risk.

Impact

An authenticated user can bypass backend authorization checks to edit issues they are not permitted to modify. This leads to unauthorized modification of issue data, impacting data integrity. There is no impact on confidentiality or availability. The CVSS score is 4.3 (medium severity), reflecting limited impact and requiring low privileges.

Summary

CVE-2026-55146 is a missing authorization vulnerability (CWE-862) in the issue_tracker backend of the LORIS application. Although the frontend enforces edit permissions on issues, the backend fails to verify these permissions correctly, permitting authenticated users to submit unauthorized changes to issues outside their permitted scope. This flaw affects LORIS versions >=16.0.0 <27.0.4 and >=28.0.0 <28.0.2. The vulnerability is resolved in versions 27.0.4 and 28.0.2. Disabling the Issue Tracker module removes access to the vulnerable endpoint if the module is not in use.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 21:52 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats