CVE-2026-10763

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% of all CVEs by exploit prediction. 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
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: None knownExposed: 0

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

PROMOD V is using insecure HTTP communication instead of HTTPS. The vulnerability is due to the lack of HTTPS support from 3rd party Digipede server.

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
36(Track)
EG Risk 36/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
Severity70% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

June 30, 2026

Last Modified

June 30, 2026

Advisory Details (1)

Auto-updated Jun 30, 2026
No patch confirmed yet.
generic

Hitachi Energy Publisher

https://publisher.hitachienergy.com/preview?DocumentID=8DBD000250&LanguageCode=en&DocumentPartId=&Action=Launch

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

Frequently asked(5)

What is CVE-2026-10763?
CVE-2026-10763 is a high vulnerability published on June 30, 2026. PROMOD V is using insecure HTTP communication instead of HTTPS. The vulnerability is due to the lack of HTTPS support from 3rd party Digipede server.
When was CVE-2026-10763 disclosed?
CVE-2026-10763 was first published in the National Vulnerability Database on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10763 actively exploited?
CVE-2026-10763 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.2% of all scored CVEs.
What is the CVSS score of CVE-2026-10763?
CVE-2026-10763 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-10763?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10763, 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-10763

Explore →

Is Your Infrastructure Affected by CVE-2026-10763?

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

Start Free Scan →Browse All CVEs