LiveActive security incident?Get immediate response
CVE Record

CVE-2026-16897: Vulnerabilities in IBM AIX and PowerVM VIOS

IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a local attacker to cause a denial of service due to an out-of-bounds write.

MediumCVSS 4.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A highly privileged local user could crash affected IBM AIX or PowerVM VIOS systems, disrupting services hosted on them. The issue does not indicate remote compromise or data theft. Business risk is concentrated where these platforms support critical workloads or untrusted administrators have privileged access.

Executive priority

Treat as a scheduled, risk-based remediation rather than an emergency internet-wide response. Expedite changes for critical IBM Power environments where a system crash would cause material operational disruption or privileged access is broadly delegated.

Technical view

CVE-2026-16897 affects IBM AIX 7.2 and 7.3 and PowerVM VIOS 4.1. IBM describes an out-of-bounds write causing denial of service. CVSS 3.1 is 4.4: local access, low complexity, high privileges, no user interaction, and high availability impact without confidentiality or integrity impact.

Likely exposure

Exposure requires an affected operating-system version and a local attacker with high privileges. Internet reachability alone does not establish exploitability. Priority increases for shared administration environments and systems supporting availability-sensitive production workloads.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not identified as being in KEV. No public exploit evidence is supplied. The stated prerequisites—local access and high privileges—substantially limit the attacker population but do not eliminate insider or post-compromise risk.

Researcher notes

The supplied description identifies an out-of-bounds write, while the listed CWE-369 denotes divide-by-zero. This inconsistency prevents confidently characterizing the underlying defect. Researchers should rely on IBM's advisory for authoritative technical and remediation details. The bundle provides no affected component name, exploit evidence, or specific fix level.

Mitigation direction

  • Review IBM advisory 7283858 for applicable fixes and installation requirements.
  • Apply IBM-provided remediation to affected AIX and VIOS systems under normal change controls.
  • Restrict local privileged access until remediation is verified.
  • Prioritize systems whose failure would interrupt critical workloads.

Validation and detection

  • Inventory AIX 7.2, AIX 7.3, and PowerVM VIOS 4.1 deployments.
  • Compare installed maintenance levels against IBM advisory 7283858.
  • Confirm remediation succeeded using IBM's verification guidance.
  • Review whether privileged local access is limited to authorized administrators.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-369: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-16897 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.4CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H0.83.6ibm

Vulnerability scoring details

Base CVSS 3.1 score

4.4Medium
CVSS 3.1 vector shape for CVE-2026-16897Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMAIX7.2, 7.3Listed
IBMPowerVM VIOS4.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-369 · source CWE mapping

Divide By Zero

Divide By Zero represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.