CVE-2026-3144

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-08) is not newer than that change (2026-07-10), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

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.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 8, 2026

Last Modified

July 10, 2026

Advisory Details (1)

Auto-updated Oct 11, 2026
Fix referenced — no release confirmed yet.
Web pageMentions a patch (unverified)

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 12× in last 7d / 48× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 352 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 253 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-3144?
CVE-2026-3144 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-3144 published?
The CVE record for CVE-2026-3144 was published on July 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 10, 2026; the record at its source may have been updated since.
Is CVE-2026-3144 actively exploited?
CVE-2026-3144 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-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?
A fix for CVE-2026-3144 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-3144 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs