CVE-2026-75624

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-11. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

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

IBM App Connect Enterprise 13.0.1.0 through 13.0.8.1, and 12.0.1.0 through 12.0.12.27 could allow a remote authenticated attacker to bypass security restrictions due to incorrect authorization.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
40%
KEV
Not listed

Published

September 10, 2026

Last Modified

September 16, 2026

Advisory Details (1)

Auto-updated Sep 10, 2026
No patch confirmed yet.
generic

Security Bulletin: IBM App Connect Enterprise is vulnerable to privilege escalation and Denial of Service (CVE-2026-75624)

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-75624?
CVE-2026-75624 is a high vulnerability published on September 10, 2026. IBM App Connect Enterprise 13.0.1.0 through 13.0.8.1, and 12.0.1.0 through 12.0.12.27 could allow a remote authenticated attacker to bypass security restrictions due to incorrect authorization.
When was CVE-2026-75624 disclosed?
CVE-2026-75624 was first published in the National Vulnerability Database on September 10, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-75624 actively exploited?
CVE-2026-75624 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 59.7% of all scored CVEs.
What is the CVSS score of CVE-2026-75624?
CVE-2026-75624 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-75624?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75624, 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-75624

Explore →

Is Your Infrastructure Affected by CVE-2026-75624?

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

Book a Demo →Browse All CVEs