CVE-2026-16817

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-19. A secondary CVSS source baseline 7.5; 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
7.5EG
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: 0.5%CVSS: 7.5Exploit: 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 AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to a NULL pointer dereference.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.5% × 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 partial (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 at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend 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 at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

August 19, 2026

Last Modified

August 20, 2026

Advisory Details (1)

Auto-updated Aug 19, 2026
Fix referenced — no release confirmed yet.
Web page

Security Bulletin: Vulnerabilities in IBM AIX and PowerVM VIOS

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

Vendor Advisories for CVE-2026-16817(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 18× in last 7d / 92× 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 191 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 91 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16817?
CVE-2026-16817 is a high-severity vulnerability; its CVE record was published on August 19, 2026. IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to cause a denial of service due to a NULL pointer dereference.
When was the CVE record for CVE-2026-16817 published?
The CVE record for CVE-2026-16817 was published on August 19, 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 August 20, 2026; the record at its source may have been updated since.
Is CVE-2026-16817 actively exploited?
CVE-2026-16817 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16817?
CVE-2026-16817 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-16817?
A fix for CVE-2026-16817 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-16817 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-16817?

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

Book a Demo →Browse All CVEs