CVE-2026-53908

MEDIUMNVD 4.34.3
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0

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

MCO is vulnerable to User Enumeration through authentication-related functionalities. The application returns distinguishable responses for valid and invalid users during username reminder and password reset operations. An attacker can leverage these differences to enumerate valid usernames and email addresses.

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
4.3
EG Score
4.3(high)
EPSS
23.8%
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-53908(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 22× in last 7d / 22× 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-06 16:27 UTCEG score recompute 2.60
  2. 2026-07-06 16:27 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:21 UTCGHSA enrichment
  6. 2026-07-06 15:08 UTCNVD updateCVSS v3 → 4.3
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 15:50 UTCEG score recompute
  10. 2026-07-05 15:50 UTCGHSA enrichment
  11. 2026-07-05 02:31 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 15:21 UTCEG score recompute
  14. 2026-07-04 15:20 UTCGHSA enrichment
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-04 06:31 UTCEPSS rescore
  17. 2026-07-03 14:50 UTCEG score recompute
  18. 2026-07-03 14:50 UTCGHSA enrichment
  19. 2026-07-02 14:21 UTCEG score recompute
  20. 2026-07-02 14:21 UTCGHSA enrichment
  21. 2026-07-01 13:53 UTCEG score recompute
  22. 2026-07-01 13:52 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-53908?
CVE-2026-53908 is a medium vulnerability published on July 1, 2026. MCO is vulnerable to User Enumeration through authentication-related functionalities. The application returns distinguishable responses for valid and invalid users during username reminder and password reset operations. An attacker can leverage these differences to enumerate valid usernames and…
When was CVE-2026-53908 disclosed?
CVE-2026-53908 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-53908 actively exploited?
CVE-2026-53908 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53908?
CVE-2026-53908 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-53908?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53908, 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-53908

Explore →

Is Your Infrastructure Affected by CVE-2026-53908?

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