CVE-2026-53906

HIGHNVD 8.28.2
EchelonGraph scoreHIGH confidence

Score 8.2 from GitHub Security Advisory published 2026-07-01. NVD baseline CVSS 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

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

MCO is vulnerable to Path Disclosure and Path Traversal in file handling functionality related to data export and upload. Improper validation of the filename parameter allows writing files to arbitrary locations as well as indirect disclosure of absolute server paths through error messages.

Because vendor contact attempts were unsuccessful, the vulnerability has only been confirmed in version 25.3.3.1 but may also affect other versions.

CVSS v3
8.2
EG Score
8.2(high)
EG Risk
42(Track)
EG Risk 42/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
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
26.4%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 6, 2026

Advisory Details (2)

Auto-updated Jul 3, 2026
No patch confirmed yet.
generic

MyComplianceOffice | Compliance Management Software

https://mco.mycomplianceoffice.com/
generic

Vulnerabilities in MyComplianceOffice MCO software | CERT Polska

https://cert.pl/en/posts/2026/07/CVE-2026-53902

Vendor Advisories for CVE-2026-53906(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 10× in last 7d / 64× 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-07-24 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:19 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-16 23:55 UTCGHSA enrichment
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-16 11:54 UTCGHSA enrichment
  14. 2026-07-15 23:53 UTCGHSA enrichment
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 11:52 UTCGHSA enrichment
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-15 02:00 UTCEPSS rescore
  20. 2026-07-14 23:50 UTCGHSA enrichment
  21. 2026-07-14 11:49 UTCGHSA enrichment
  22. 2026-07-13 23:48 UTCGHSA enrichment
  23. 2026-07-13 22:31 UTCEPSS rescore
  24. 2026-07-13 11:47 UTCGHSA enrichment
  25. 2026-07-13 06:13 UTCEPSS rescore
Show 39 more
  1. 2026-07-13 06:13 UTCEPSS rescore
  2. 2026-07-12 23:43 UTCGHSA enrichment
  3. 2026-07-12 11:41 UTCGHSA enrichment
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-11 23:38 UTCGHSA enrichment
  6. 2026-07-11 11:37 UTCGHSA enrichment
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-10 23:35 UTCGHSA enrichment
  10. 2026-07-10 11:32 UTCGHSA enrichment
  11. 2026-07-09 23:28 UTCGHSA enrichment
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-09 11:27 UTCGHSA enrichment
  15. 2026-07-08 23:25 UTCGHSA enrichment
  16. 2026-07-08 15:16 UTCEPSS rescore
  17. 2026-07-08 15:16 UTCEPSS rescore
  18. 2026-07-08 11:24 UTCGHSA enrichment
  19. 2026-07-07 23:23 UTCGHSA enrichment
  20. 2026-07-07 13:46 UTCEPSS rescore
  21. 2026-07-07 13:46 UTCEPSS rescore
  22. 2026-07-07 11:23 UTCGHSA enrichment
  23. 2026-07-06 23:21 UTCEG score recompute 3.10
  24. 2026-07-06 23:21 UTCGHSA enrichment
  25. 2026-07-06 16:27 UTCEPSS rescore
  26. 2026-07-06 16:27 UTCEPSS rescore
  27. 2026-07-06 15:08 UTCNVD updateCVSS v3 → 8.2 · severity → HIGH
  28. 2026-07-06 02:23 UTCEPSS rescore
  29. 2026-07-06 02:23 UTCEPSS rescore
  30. 2026-07-05 21:28 UTCGHSA enrichment
  31. 2026-07-05 02:31 UTCEPSS rescore
  32. 2026-07-05 02:30 UTCEPSS rescore
  33. 2026-07-04 19:34 UTCGHSA enrichment
  34. 2026-07-04 06:31 UTCEPSS rescore
  35. 2026-07-04 06:31 UTCEPSS rescore
  36. 2026-07-03 17:40 UTCGHSA enrichment
  37. 2026-07-02 15:47 UTCGHSA enrichment
  38. 2026-07-01 13:53 UTCEG score recompute
  39. 2026-07-01 13:52 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53906?
CVE-2026-53906 is a high vulnerability published on July 1, 2026. MCO is vulnerable to Path Disclosure and Path Traversal in file handling functionality related to data export and upload. Improper validation of the filename parameter allows writing files to arbitrary locations as well as indirect disclosure of absolute server paths through error messages. Because…
When was CVE-2026-53906 disclosed?
CVE-2026-53906 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53906 actively exploited?
CVE-2026-53906 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 26.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53906?
CVE-2026-53906 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-53906?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53906, 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-53906

Explore →

Is Your Infrastructure Affected by CVE-2026-53906?

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