CVE-2026-8636

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.5EG
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.5Exploit: None knownExposed: 0

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

IBM Datacap 9.1.7, 9.1.8, and 9.1.9 and IBM Datacap Navigator 9.1.7, 9.1.8, and 9.1.9 allows an attacker to retrieve user passwords and cryptographic keys from memory. Attacker can use the same keys to decrypt password, gain access to the application and access sensitive data in the database.

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

Published

June 22, 2026

Last Modified

June 26, 2026

Advisory Details (1)

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

Security Bulletin: Multiple Vulnerabilities in IBM Datacap

https://www.ibm.com/support/pages/node/7276609

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

Frequently asked(5)

What is CVE-2026-8636?
CVE-2026-8636 is a high vulnerability published on June 22, 2026. IBM Datacap 9.1.7, 9.1.8, and 9.1.9 and IBM Datacap Navigator 9.1.7, 9.1.8, and 9.1.9 allows an attacker to retrieve user passwords and cryptographic keys from memory. Attacker can use the same keys to decrypt password, gain access to the application and access sensitive data in the database.
When was CVE-2026-8636 disclosed?
CVE-2026-8636 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8636 actively exploited?
CVE-2026-8636 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 95.7% of all scored CVEs.
What is the CVSS score of CVE-2026-8636?
CVE-2026-8636 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-8636?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8636, 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-8636

Explore →

Is Your Infrastructure Affected by CVE-2026-8636?

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

Start Free Scan →Browse All CVEs