CVE-2026-95703

MEDIUMPre-NVD 5.15.1
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: secondary
Trending — 4 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: 1%CVSS: 5.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In MISP, the OrganisationsController::__uploadLogo method processed a caller-supplied tmp_name value with filesystem probes (file_exists, MIME type detection, EXIF reading) before verifying that the value corresponded to a genuine PHP file upload via is_uploaded_file. An authenticated site-admin user could supply an arbitrary server file path as the tmp_name parameter. The application would then probe that path and return distinct validation error messages depending on whether the file existed and what its image type was, effectively creating a file-existence and image-type oracle against the server filesystem.

The vulnerability requires site-admin privileges and does not allow arbitrary file read, code execution, or modification; the impact is limited to disclosure of whether a given path exists on the server and, for image files, their type.

CVSS v3
5.1
EG Score
5.1(low)
EG Risk
27(Track)
EG Risk 27/100SSVC: Track

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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

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 12eaadc9e (MISP/MISP)

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

https://github.com/MISP/MISP/commit/12eaadc9e

Vendor Advisories for CVE-2026-95703(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 6× 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-09-23 17:54 UTCEPSS rescore
  2. 2026-09-23 16:19 UTCGHSA enrichment
  3. 2026-09-22 16:20 UTCGHSA enrichment
  4. 2026-09-22 15:19 UTCEG score recompute
  5. 2026-09-22 14:55 UTCEG score recompute
  6. 2026-09-22 14:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-95703?
CVE-2026-95703 is a medium vulnerability published on September 22, 2026. In MISP, the OrganisationsController::uploadLogo method processed a caller-supplied tmpname value with filesystem probes (fileexists, MIME type detection, EXIF reading) before verifying that the value corresponded to a genuine PHP file upload via isuploadedfile. An authenticated site-admin user…
When was CVE-2026-95703 disclosed?
CVE-2026-95703 was first published in the National Vulnerability Database 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-95703 actively exploited?
CVE-2026-95703 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.6% of all scored CVEs.
What is the CVSS score of CVE-2026-95703?
CVE-2026-95703 has a CVSS v3 base score of 5.1 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-95703?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-95703, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-95703?

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