CVE-2026-95701

MEDIUMPre-NVD 5.15.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8% (53rd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
5.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 5.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In MISP, the __statisticsOrgs method in UsersController.php used the organization name directly as a file-system path component when checking for the existence of an organization logo image. The original code called file_exists() with a path constructed as APP . 'webroot' . DS . 'img' . DS . 'orgs' . DS . $k . '.png', where $k is the organization name. Because the referenced directory (app/webroot/img/orgs) no longer exists in current MISP deployments (org logos were relocated to files/img/orgs), the check was functionally dead and never triggered. However, the underlying pattern—concatenating an attacker-influenced organization name into a file path without sanitization—constitutes a path traversal weakness. An organization name containing directory traversal sequences (e.g., '../../../../etc/passwd') would, if the target directory existed, allow an authenticated user with the ability to create or rename an organization to probe for the existence of arbitrary files on the server.

CVSS v3
5.1
EG Score
5.1MEDIUMmedium confidence
EG Risk
28
EG Risk 28/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity51% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
53rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 22, 2026

Last Modified

September 22, 2026

Advisory Details (1)

Auto-updated Sep 22, 2026
Patch available. Sources: github_commit.
github_commit Patch Available

commit a2f7cba6e (MISP/MISP)

Patch available: MISP/MISP v2.5.47 (contains commit a2f7cba6e)

https://github.com/MISP/MISP/commit/a2f7cba6e

Vendor Advisories for CVE-2026-95701(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-04 05:32 UTCEG score recompute
  2. 2026-10-04 05:31 UTCGHSA enrichment
  3. 2026-10-03 14:26 UTCEPSS rescore
  4. 2026-10-03 04:24 UTCEG score recompute
  5. 2026-10-03 04:24 UTCGHSA enrichment
  6. 2026-10-02 17:57 UTCEPSS rescore
  7. 2026-10-02 03:15 UTCEG score recompute
  8. 2026-10-02 03:15 UTCGHSA enrichment
  9. 2026-10-01 19:51 UTCEPSS rescore
  10. 2026-10-01 02:06 UTCEG score recompute
  11. 2026-10-01 02:06 UTCGHSA enrichment
  12. 2026-09-30 15:04 UTCEPSS rescore
  13. 2026-09-30 00:58 UTCEG score recompute
  14. 2026-09-30 00:58 UTCGHSA enrichment
  15. 2026-09-28 23:50 UTCEG score recompute
  16. 2026-09-28 23:50 UTCGHSA enrichment
  17. 2026-09-28 13:52 UTCEPSS rescore
  18. 2026-09-28 13:52 UTCEPSS rescore
  19. 2026-09-27 22:38 UTCEG score recompute
  20. 2026-09-27 22:38 UTCGHSA enrichment
  21. 2026-09-27 13:49 UTCEPSS rescore
  22. 2026-09-26 21:30 UTCEG score recompute
  23. 2026-09-26 21:30 UTCGHSA enrichment
  24. 2026-09-26 15:59 UTCEPSS rescore
  25. 2026-09-25 20:22 UTCGHSA enrichment
Show 9 more
  1. 2026-09-24 18:37 UTCEG score recompute
  2. 2026-09-24 18:37 UTCGHSA enrichment
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-23 17:28 UTCGHSA enrichment
  6. 2026-09-22 16:20 UTCGHSA enrichment
  7. 2026-09-22 15:19 UTCEG score recompute
  8. 2026-09-22 14:50 UTCEG score recompute
  9. 2026-09-22 14:50 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-95701?
CVE-2026-95701 is a medium vulnerability published on September 22, 2026. In MISP, the statisticsOrgs method in UsersController.php used the organization name directly as a file-system path component when checking for the existence of an organization logo image. The original code called file_exists() with a path constructed as APP . 'webroot' . DS . 'img' . DS . 'orgs' .…
When was CVE-2026-95701 disclosed?
CVE-2026-95701 was first published on September 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-95701 actively exploited?
CVE-2026-95701 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-95701?
CVE-2026-95701 has a CVSS base score of 5.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-95701?
A fix for CVE-2026-95701 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-95701 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-95701

Explore →

Is Your Infrastructure Affected by CVE-2026-95701?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs