CVE-2026-16891

LOWPre-NVD 3.33.3—
EchelonGraph scoreMEDIUM confidence

Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-08-19. A secondary CVSS source baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 3.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to obtain sensitive information due to an out-of-bounds read.

CVSS v3
3.3
EG Score
3.3LOWmedium confidence
EG Risk
15
EG Risk 15/100CISA SSVC

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
Severity33% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 19, 2026

Last Modified

August 20, 2026

References (1)

Vendor Advisories for CVE-2026-16891(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 7× in last 7d / 35× 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-10-03 14:25 UTCEPSS rescore
  2. 2026-10-03 02:59 UTCEG score recompute
  3. 2026-10-03 02:59 UTCGHSA enrichment
  4. 2026-10-01 19:49 UTCEPSS rescore
  5. 2026-09-30 15:02 UTCEPSS rescore
  6. 2026-09-30 08:38 UTCEG score recompute
  7. 2026-09-30 08:38 UTCGHSA enrichment
  8. 2026-09-28 13:51 UTCEPSS rescore
  9. 2026-09-27 13:47 UTCEPSS rescore
  10. 2026-09-27 05:59 UTCEG score recompute
  11. 2026-09-27 05:59 UTCGHSA enrichment
  12. 2026-09-26 15:58 UTCEPSS rescore
  13. 2026-09-22 21:42 UTCEG score recompute
  14. 2026-09-22 21:42 UTCGHSA enrichment
  15. 2026-09-20 03:30 UTCEG score recompute
  16. 2026-09-20 03:30 UTCGHSA enrichment
  17. 2026-09-18 19:27 UTCEPSS rescore
  18. 2026-09-17 09:17 UTCEG score recompute
  19. 2026-09-17 09:17 UTCGHSA enrichment
  20. 2026-09-16 14:07 UTCEPSS rescore
  21. 2026-09-14 15:04 UTCEG score recompute
  22. 2026-09-14 15:04 UTCGHSA enrichment
  23. 2026-09-12 15:00 UTCEPSS rescore
  24. 2026-09-11 20:51 UTCEG score recompute
  25. 2026-09-11 20:51 UTCGHSA enrichment
Show 41 more
  1. 2026-09-11 14:52 UTCEPSS rescore
  2. 2026-09-11 09:36 UTCEPSS rescore
  3. 2026-09-10 09:34 UTCEPSS rescore
  4. 2026-09-09 02:39 UTCEG score recompute
  5. 2026-09-09 02:39 UTCGHSA enrichment
  6. 2026-09-08 22:00 UTCEPSS rescore
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-06 08:25 UTCEG score recompute
  10. 2026-09-06 08:25 UTCGHSA enrichment
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-03 14:13 UTCEG score recompute
  13. 2026-09-03 14:13 UTCGHSA enrichment
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-08-31 19:59 UTCEG score recompute
  17. 2026-08-31 19:59 UTCGHSA enrichment
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-29 01:47 UTCEG score recompute
  21. 2026-08-29 01:46 UTCGHSA enrichment
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-26 05:06 UTCEG score recompute
  26. 2026-08-26 05:06 UTCGHSA enrichment
  27. 2026-08-25 13:48 UTCEPSS rescore
  28. 2026-08-23 10:49 UTCEG score recompute
  29. 2026-08-23 10:49 UTCGHSA enrichment
  30. 2026-08-23 00:19 UTCEPSS rescore
  31. 2026-08-21 23:49 UTCEPSS rescore
  32. 2026-08-20 22:55 UTCEPSS rescore
  33. 2026-08-20 16:36 UTCEG score recompute
  34. 2026-08-20 16:36 UTCGHSA enrichment
  35. 2026-08-20 16:07 UTCEG score recompute
  36. 2026-08-20 16:07 UTCGHSA enrichment
  37. 2026-08-20 13:25 UTCEG score recompute
  38. 2026-08-20 13:25 UTCGHSA enrichment
  39. 2026-08-19 20:19 UTCEG score recompute
  40. 2026-08-19 20:03 UTCEG score recompute
  41. 2026-08-19 20:02 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-16891?
CVE-2026-16891 is a low vulnerability published on August 19, 2026. IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to obtain sensitive information due to an out-of-bounds read.
When was CVE-2026-16891 disclosed?
CVE-2026-16891 was first published on August 19, 2026, with the most recent update on August 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-16891 actively exploited?
CVE-2026-16891 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16891?
CVE-2026-16891 has a CVSS base score of 3.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-16891?
A fix for CVE-2026-16891 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-16891 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-16891?

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

Book a Demo →Browse All CVEs