CVE-2026-3144

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 86% 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
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

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

IBM API Connect 12.1.0.0 through 12.1.0.3 uses default credentials which could allow an attacker to gain unauthorized access to the application before the system enforces a credential update.

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

Published

July 8, 2026

Last Modified

July 10, 2026

Advisory Details (1)

Auto-updated Jul 25, 2026
Patch available.
generic Patch Available

Security Bulletin: Multiple Vulnerabilities in IBM API Connect

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

Vendor Advisories for CVE-2026-3144(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 19× in last 7d / 52× 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 06:04 UTCGHSA enrichment
  2. 2026-07-27 01:18 UTCGHSA enrichment
  3. 2026-07-26 21:00 UTCGHSA enrichment
  4. 2026-07-26 16:44 UTCEG score recompute
  5. 2026-07-26 16:44 UTCGHSA enrichment
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 12:28 UTCEG score recompute
  9. 2026-07-26 12:27 UTCGHSA enrichment
  10. 2026-07-25 14:18 UTCEPSS rescore
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-24 14:17 UTCEPSS rescore
  13. 2026-07-24 14:17 UTCEPSS rescore
  14. 2026-07-23 14:18 UTCEPSS rescore
  15. 2026-07-23 14:18 UTCEPSS rescore
  16. 2026-07-23 03:08 UTCEG score recompute▲ 1.70
  17. 2026-07-22 14:08 UTCEPSS rescore
  18. 2026-07-21 15:24 UTCEPSS rescore
  19. 2026-07-20 17:08 UTCEPSS rescore
  20. 2026-07-19 14:31 UTCEPSS rescore
  21. 2026-07-19 02:29 UTCEPSS rescore
  22. 2026-07-18 10:04 UTCEPSS rescore
  23. 2026-07-17 05:05 UTCGHSA enrichment
  24. 2026-07-16 17:03 UTCEPSS rescore
  25. 2026-07-16 17:02 UTCGHSA enrichment
Show 27 more
  1. 2026-07-16 04:32 UTCGHSA enrichment
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 16:30 UTCGHSA enrichment
  5. 2026-07-15 04:28 UTCGHSA enrichment
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-14 16:25 UTCGHSA enrichment
  8. 2026-07-14 04:23 UTCGHSA enrichment
  9. 2026-07-13 22:30 UTCEPSS rescore
  10. 2026-07-13 16:19 UTCGHSA enrichment
  11. 2026-07-13 06:13 UTCEPSS rescore
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-13 04:13 UTCGHSA enrichment
  14. 2026-07-12 16:09 UTCGHSA enrichment
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-12 04:06 UTCGHSA enrichment
  17. 2026-07-11 16:03 UTCGHSA enrichment
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-11 04:01 UTCGHSA enrichment
  20. 2026-07-10 18:19 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  21. 2026-07-10 15:58 UTCGHSA enrichment
  22. 2026-07-10 03:55 UTCGHSA enrichment
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-09 15:53 UTCGHSA enrichment
  25. 2026-07-09 03:48 UTCGHSA enrichment
  26. 2026-07-08 15:46 UTCEG score recompute
  27. 2026-07-08 15:45 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-3144?
CVE-2026-3144 is a critical vulnerability published on July 8, 2026. IBM API Connect 12.1.0.0 through 12.1.0.3 uses default credentials which could allow an attacker to gain unauthorized access to the application before the system enforces a credential update.
When was CVE-2026-3144 disclosed?
CVE-2026-3144 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3144 actively exploited?
CVE-2026-3144 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 85.6% of all scored CVEs.
What is the CVSS score of CVE-2026-3144?
CVE-2026-3144 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-3144?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3144, 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-3144

Explore →

Is Your Infrastructure Affected by CVE-2026-3144?

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

Start Free Scan →Browse All CVEs