CVE-2026-16606

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-22. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (Fsas Technologies) lists Fujitsu Linux openFT versions up to and including 12.1C96; Fujitsu Oracle Solaris openFT versions up to and including 12.1C95 as affected, and Fujitsu Linux openFT versions 12.1D00; Fujitsu Oracle Solaris openFT versions 12.1D00 as unaffected. No release containing a fix is confirmed on record.

A vulnerability in Fujitsu Software Linux openFT and Fujitsu Software Oracle Solaris openFT before version 12.1D00 allows for unauthenticated remote code execution (pre-auth RCE) on GNU/Linux or Oracle Solaris. The Fsas Technologies PSIRT obtained that intelligence internally and covers the CVE beyond its CNA scope under existing agreement with Fujitsu Germany.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
1.1%
EPSS %ILE
66th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-18). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 22, 2026

Last Modified

July 22, 2026

Vendor Advisories for CVE-2026-16606(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 / 64× 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 100 of 418 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. None are among the latest 100 rows. The 318 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-16606?
CVE-2026-16606 is a critical-severity vulnerability; its CVE record was published on July 22, 2026. A vulnerability in Fujitsu Software Linux openFT and Fujitsu Software Oracle Solaris openFT before version 12.1D00 allows for unauthenticated remote code execution (pre-auth RCE) on GNU/Linux or Oracle Solaris. The Fsas Technologies PSIRT obtained that intelligence internally and covers the CVE…
When was CVE-2026-16606 made public?
CVE-2026-16606 was made public on July 22, 2026: that is the date its CVE record's CNA, Fsas Technologies, gives for when the vulnerability was made public. The CVE record itself was published on July 22, 2026. EchelonGraph's copy of the record carries a last-modified date of July 22, 2026; the record at its source may have been updated since.
Is CVE-2026-16606 actively exploited?
CVE-2026-16606 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (66th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16606?
CVE-2026-16606 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-16606?
No fix for CVE-2026-16606 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 CVE record's CNA (Fsas Technologies) lists Fujitsu Linux openFT versions up to and including 12.1C96; Fujitsu Oracle Solaris openFT versions up to and including 12.1C95 as affected, and Fujitsu Linux openFT versions 12.1D00; Fujitsu Oracle Solaris openFT versions 12.1D00 as unaffected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-16606 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-16606?

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