CVE-2026-16891

LOWPre-NVD 3.33.3
EchelonGraph scoreHIGH 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: ghsa, secondary
Trending — 4 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%CVSS: 3.3Exploit: None knownExposed: 0

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

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.3(high)
EG Risk
15(Track)
EG Risk 15/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
Severity33% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 20, 2026

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 10× in last 7d / 10× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 16:36 UTCEG score recompute
  3. 2026-08-20 16:36 UTCGHSA enrichment
  4. 2026-08-20 16:07 UTCEG score recompute
  5. 2026-08-20 16:07 UTCGHSA enrichment
  6. 2026-08-20 13:25 UTCEG score recompute
  7. 2026-08-20 13:25 UTCGHSA enrichment
  8. 2026-08-19 20:19 UTCEG score recompute
  9. 2026-08-19 20:03 UTCEG score recompute
  10. 2026-08-19 20:02 UTCMITRE cvelistV5first tracked

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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 96.5% of all scored CVEs.
What is the CVSS score of CVE-2026-16891?
CVE-2026-16891 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-16891?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16891, 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-16891

Explore →

Is Your Infrastructure Affected by CVE-2026-16891?

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