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 22.0.0 prior to 27.0.4 and from 28.0.0 prior to 28.0.2, the API for the imaging_browser module permits edits to imaging data without checking the frontend permissions that restrict editing in Imaging Browser. An authenticated API caller can therefore modify imaging data without the required edit authorization. Deployments that no longer use the API can disable it to remove access to this endpoint. This issue is fixed in versions 27.0.4 and 28.0.2.
CVE-2026-55147
MEDIUMPre-NVD 6.36.3Trending — 4 sources updated this week
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (11th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Also known asEUVD-2026-114516 (ENISA EUVD)Source: ENISA EUVD
6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.3Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 6.3
- EG Score
- 6.3MEDIUMmedium confidence
- EG Risk
- 28EG Risk 28/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity63% × 45%Impact severity (EG Severity): CVSS 6.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.2% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.2%
- EPSS %ILE
- 11th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (6.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 6.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 30, 2026
Last Modified
November 2, 2026
Advisory Details (5)
Auto-updated Oct 30, 2026Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available
LORIS 28.0.2
Patch available: aces/Loris v28.0.2
https://github.com/aces/Loris/releases/tag/v28.0.2GitHub release Patch Available
LORIS Release 27.0.4
Patch available: aces/Loris v27.0.4
https://github.com/aces/Loris/releases/tag/v27.0.4GitHub commit Patch Available
commit b13053597530 (aces/Loris)
Patch available: aces/Loris v27.0.4 (contains commit b13053597530)
https://github.com/aces/Loris/commit/b13053597530ee33fbced35085d2490bc9ccc03aGitHub pull request Patch Available
Merge 27.0 into the 28 branch
Patch available: aces/Loris v28.0.2 (PR #10531 merged 2026-06-10)
https://github.com/aces/Loris/pull/10531GitHub advisoryMentions a patch (unverified)
Incorrect access checks in API for Imaging Browser · Advisory · aces/Loris · GitHub
https://github.com/aces/Loris/security/advisories/GHSA-m48r-jv24-jjcxWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-02 19:48 UTCEG score recompute
- 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-11-02 15:28 UTCEG score recompute
- 2026-11-02 14:48 UTCEG score recompute
- 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-30 23:02 UTCENISA EUVD ID recordedEUVD-2026-114516 · Source: ENISA EUVD
- 2026-10-30 22:26 UTCEG score recompute
- 2026-10-30 21:39 UTCEG score recomputeFirst assessed: 6.3 MEDIUM
- 2026-10-30 21:38 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-55147?
CVE-2026-55147 is a medium-severity vulnerability; its CVE record was published on October 30, 2026. 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 22.0.0 prior to 27.0.4 and from 28.0.0 prior to 28.0.2, the API for the imaging_browser module permits edits to imaging…
When was the CVE record for CVE-2026-55147 published?
The CVE record for CVE-2026-55147 was published on October 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 2, 2026; the record at its source may have been updated since.
Is CVE-2026-55147 actively exploited?
CVE-2026-55147 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55147?
CVE-2026-55147 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55147?
A fix for CVE-2026-55147 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-55147
Is Your Infrastructure Affected by CVE-2026-55147?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.