CVE-2026-26985
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedLORIS (Longitudinal Online Research and Imaging System) is a self-hosted web application that provides data- and project-management for neuroimaging research. Starting in version 24.0.0 and prior to versions 26.0.5, 27.0.2, and 28.0.0, an authenticated user with the appropriate authorization can read configuration files on the server by exploiting a path traversal vulnerability. Some of these files contain hard-coded credentials. The vulnerability allows an attacker to read configuration files containing hard-coded credentials. The attacker could then authenticate to the database or other services if those credentials are reused. The attacker must be authenticated and have the required permissions. However, the vulnerability is easy to exploit and the application source code is public. This problem is fixed in LORIS v26.0.5 and v27.0.2 and above, and v28.0.0 and above. As a workaround, the electrophysiogy_browser in LORIS can be disabled by an administrator using the module manager.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA path traversal vulnerability in LORIS versions 24.0.0 through versions prior to 26.0.5, 27.0.2, and 28.0.0 allows authenticated users with appropriate permissions to read arbitrary server files via the electrophysiology_browser module. This enables reading configuration files containing hard-coded credentials that could be reused for database or service authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 24.0.0, < 26.0.5>= 27.0.0, < 27.0.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check LORIS version installedLocate the LORIS codebase and identify the version from release tags, composer.json, or a version configuration file. Common paths include the root directory or a config file like VERSION or Core.pm.Affected if The installed version falls within >= 24.0.0 and < 26.0.5, OR >= 27.0.0 and < 27.0.2, OR equals 28.0.0.
-
Verify electrophysiology_browser module is enabledAccess the LORIS module manager or configuration database table (e.g., the modules table) to determine if the electrophysiology_browser module is currently active/enabled.Affected if The electrophysiology_browser module is enabled in the LORIS configuration.
-
Confirm user permissions for electrophysiology_browserReview user permission settings in the LORIS user management interface or permission tables to identify which authenticated users have access to the electrophysiology_browser module.Affected if Any authenticated user account has been granted permission to access the electrophysiology_browser module.
A user is affected if their LORIS version is within the vulnerable ranges AND the electrophysiology_browser module is enabled with accessible user permissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped26.0.527.0.2
Upgrade LORIS to v26.0.5/v27.0.2/v28.0.0 or later to patch the path traversal vulnerability. Alternatively, disable the electrophysiology_browser module via the module manager as a workaround.
LORIS v26.0.5, v27.0.2, or v28.0.0 (or later) - recommend latest stable v28.0.x release
- 1. Identify the currently installed LORIS version by checking the application's version information or configuration files
- 2. If running version 24.0.0 through 26.0.4, plan upgrade to v26.0.5 or later (or v28.0.0+)
- 3. If running version 27.0.0 or 27.0.2, plan upgrade to v27.0.2 or later (or v28.0.0+)
- 4. Perform a complete backup of the LORIS database, configuration files, and installation directory
- 5. Test the upgrade in a non-production/staging environment first
- 6. Execute the upgrade to the chosen fixed version following LORIS upgrade documentation
- 7. Verify the path traversal vulnerability is remediated by confirming configuration files are no longer accessible via traversal
- 8. As an alternative workaround only if upgrading is not immediately feasible: Log in as administrator, navigate to the Module Manager, and disable the electrophysiology_browser module
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26985 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-26985 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data