CVE-2026-3602

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.5Exploit: None knownExposed services: Not assessed

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

IBM App Connect Enterprise 13.0.1.0 through 13.0.7.2, and 12.0.1.0 through 12.0.12.26 and IBM Integration Bus for z/OS 10.1.0.0 through 10.1.0.7 is vulnerable to SQL injection. A remote attacker could socially engineer a user into accidentally creating files they may not be aware of.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

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
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

Published

June 30, 2026

Last Modified

July 20, 2026

Advisory Details (1)

Auto-updated Jun 30, 2026
No fix on record yet.
generic

Security Bulletin: IBM App Connect Enterprise and IBM Integration Bus for z/OS toolkit is vulnerable to an sql injection (CVE-2026-3602)

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

Vendor Advisories for CVE-2026-3602(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 7× in last 7d / 31× 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.

Showing the most recent 100 of 185 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:17 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-28 13:51 UTCEPSS rescore
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-26 15:58 UTCEPSS rescore
  13. 2026-09-26 00:26 UTCEPSS rescore
  14. 2026-09-23 07:17 UTCEG score recompute
  15. 2026-09-23 07:17 UTCGHSA enrichment
  16. 2026-09-20 20:15 UTCEPSS rescore
  17. 2026-09-18 19:28 UTCEPSS rescore
  18. 2026-09-18 19:28 UTCEPSS rescore
  19. 2026-09-18 06:48 UTCEG score recompute
  20. 2026-09-18 06:48 UTCGHSA enrichment
  21. 2026-09-17 19:30 UTCEPSS rescore
  22. 2026-09-16 14:08 UTCEPSS rescore
  23. 2026-09-16 05:15 UTCEPSS rescore
  24. 2026-09-15 03:11 UTCEPSS rescore
  25. 2026-09-14 00:46 UTCEG score recompute
Show 75 more
  1. 2026-09-14 00:46 UTCGHSA enrichment
  2. 2026-09-13 16:47 UTCEPSS rescore
  3. 2026-09-12 15:08 UTCEG score recompute
  4. 2026-09-12 15:08 UTCGHSA enrichment
  5. 2026-09-12 15:01 UTCEPSS rescore
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 14:34 UTCEG score recompute
  11. 2026-09-06 14:34 UTCGHSA enrichment
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:39 UTCEPSS rescore
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 17:57 UTCEG score recompute
  19. 2026-08-30 17:57 UTCGHSA enrichment
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:41 UTCEPSS rescore
  22. 2026-08-27 22:40 UTCEG score recompute
  23. 2026-08-27 22:40 UTCGHSA enrichment
  24. 2026-08-27 14:25 UTCEPSS rescore
  25. 2026-08-26 14:46 UTCEPSS rescore
  26. 2026-08-25 13:49 UTCEPSS rescore
  27. 2026-08-24 11:37 UTCEG score recompute
  28. 2026-08-24 11:37 UTCGHSA enrichment
  29. 2026-08-23 08:26 UTCEG score recompute
  30. 2026-08-23 08:26 UTCGHSA enrichment
  31. 2026-08-23 00:19 UTCEPSS rescore
  32. 2026-08-22 08:11 UTCEG score recompute
  33. 2026-08-22 08:11 UTCGHSA enrichment
  34. 2026-08-21 23:49 UTCEPSS rescore
  35. 2026-08-21 06:03 UTCEG score recompute
  36. 2026-08-21 06:03 UTCGHSA enrichment
  37. 2026-08-20 22:55 UTCEPSS rescore
  38. 2026-08-20 05:49 UTCEG score recompute
  39. 2026-08-20 05:49 UTCGHSA enrichment
  40. 2026-08-19 17:03 UTCEPSS rescore
  41. 2026-08-19 05:34 UTCEG score recompute
  42. 2026-08-19 05:34 UTCGHSA enrichment
  43. 2026-08-18 13:48 UTCEPSS rescore
  44. 2026-08-18 05:01 UTCEG score recompute
  45. 2026-08-18 05:01 UTCGHSA enrichment
  46. 2026-08-17 13:47 UTCEPSS rescore
  47. 2026-08-17 02:37 UTCEG score recompute
  48. 2026-08-17 02:37 UTCGHSA enrichment
  49. 2026-08-16 14:56 UTCEPSS rescore
  50. 2026-08-16 02:22 UTCEG score recompute
  51. 2026-08-16 02:22 UTCGHSA enrichment
  52. 2026-08-16 02:14 UTCEPSS rescore
  53. 2026-08-15 02:08 UTCEG score recompute
  54. 2026-08-15 02:08 UTCGHSA enrichment
  55. 2026-08-15 01:30 UTCEPSS rescore
  56. 2026-08-14 01:54 UTCEG score recompute
  57. 2026-08-14 01:54 UTCGHSA enrichment
  58. 2026-08-13 22:00 UTCEPSS rescore
  59. 2026-08-13 01:40 UTCEG score recompute
  60. 2026-08-13 01:40 UTCGHSA enrichment
  61. 2026-08-12 13:51 UTCEPSS rescore
  62. 2026-08-12 01:26 UTCEG score recompute
  63. 2026-08-12 01:26 UTCGHSA enrichment
  64. 2026-08-11 13:43 UTCEPSS rescore
  65. 2026-08-11 01:12 UTCEG score recompute
  66. 2026-08-11 01:12 UTCGHSA enrichment
  67. 2026-08-11 00:00 UTCEPSS rescore
  68. 2026-08-10 00:59 UTCEG score recompute
  69. 2026-08-10 00:59 UTCGHSA enrichment
  70. 2026-08-09 13:46 UTCEPSS rescore
  71. 2026-08-09 00:45 UTCEG score recompute
  72. 2026-08-09 00:45 UTCGHSA enrichment
  73. 2026-08-08 16:37 UTCEPSS rescore
  74. 2026-08-08 00:30 UTCEG score recompute
  75. 2026-08-08 00:30 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-3602?
CVE-2026-3602 is a medium vulnerability published on June 30, 2026. IBM App Connect Enterprise 13.0.1.0 through 13.0.7.2, and 12.0.1.0 through 12.0.12.26 and IBM Integration Bus for z/OS 10.1.0.0 through 10.1.0.7 is vulnerable to SQL injection. A remote attacker could socially engineer a user into accidentally creating files they may not be aware of.
When was CVE-2026-3602 disclosed?
CVE-2026-3602 was first published on June 30, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3602 actively exploited?
CVE-2026-3602 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-3602?
CVE-2026-3602 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-3602?
No fix for CVE-2026-3602 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-3602 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-3602

Explore →

Is Your Infrastructure Affected by CVE-2026-3602?

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