Safeguard
Vulnerability Analysis•

CVE-2026-16935: High TOCTOU Privilege Flaw in IBM AIX and VIOS

IBM AIX 7.2 and 7.3 and PowerVM VIOS 4.1 have a high severity (CVSS 7.8) TOCTOU race that allows privilege escalation. Apply the IBM fix pack.

Safeguard Security Team
4 min read

CVE-2026-16935 is a high severity (CVSS 7.8) time-of-check to time-of-use race condition in IBM AIX 7.2 and 7.3 and PowerVM VIOS 4.1. A local attacker could elevate privileges. IBM fixes it through service packs and VIOS fix packs, and the bulletin lists the affected filesets and levels.

What's affected

IBM AIX 7.2 and 7.3, and IBM PowerVM VIOS 4.1. IBM's bulletin lists the affected fileset as bos.mp64 at these levels:

  • AIX 7.2.5: 7.2.5.0 through 7.2.5.212
  • AIX 7.3.2: 7.3.2.0 through 7.3.2.5
  • AIX 7.3.3: 7.3.3.0 through 7.3.3.2
  • AIX 7.3.4: 7.3.4.0 through 7.3.4.1

The same bulletin covers a large group of AIX and VIOS issues, and one set of fixes addresses all of them. Per the bulletin, the remediation levels are AIX 7.2 TL05 SP13, AIX 7.3 TL02 SP5, AIX 7.3 TL03 SP3 and AIX 7.3 TL04 SP2, and VIOS fix packs 4.1.0.50, 4.1.1.30 and 4.1.2.20. The service packs and fix packs are cumulative.

How to check if you're exposed

Run these on each AIX LPAR and on each VIOS:

oslevel -s
lslpp -L | grep -i bos.mp64

On a VIOS, log in as padmin and run ioslevel. Compare the bos.mp64 level against the ranges above. If the fileset is at or below the upper level for its release, the system is in scope. You can also check for the APAR that matches your release with instfix -ik IJ59565 (use IJ59566 for 7.2.5, IJ59565 for 7.3.2, IJ59564 for 7.3.3 and IJ59563 for 7.3.4).

What to do now

  1. List every AIX and VIOS system and record oslevel -s or ioslevel output.
  2. Compare each against the bos.mp64 ranges in IBM's bulletin 7283858.
  3. Download the matching service pack or VIOS fix pack from Fix Central. Plan for an LPAR reboot, or use AIX Live Update where it suits you.
  4. If you patch through NIM with nimsh secure, read the IBM note linked in the bulletin first, because the protocol between master and client changed.
  5. On VIOS 4.1.0 and 4.1.1, follow the post-update Postgres15 migration steps IBM links in the bulletin.
  6. Re-run the version check and record the new level.

Why it matters

This is the second TOCTOU race in the same IBM bulletin, alongside CVE-2026-16927. CWE-367 describes a gap between checking a condition and using the result, during which an attacker can alter the object being checked.

The record rates this one at 7.8, the highest local score in the group, with low complexity, low privileges and no user interaction. Two race conditions with different scores in one bulletin is a reminder that IBM scores each on its own conditions. The fix is the same cumulative pack, so apply it once and verify.

The weakness class here is CWE-367 (Time-of-check Time-of-use Race Condition). The NVD record scores it 7.8, which is high severity. IBM's bulletin gives the same score. The CVSS vector reads attack vector with local access, low attack complexity, low privileges required, no user interaction. Scope is unchanged. Impact on confidentiality, integrity and availability is rated high, high and high. The record's KEV flag is false, so this CVE is not in CISA's Known Exploited Vulnerabilities catalog, and the advisory I fetched does not report exploitation.

Safeguard's Gold directory tracks this CVE, and reachability analysis helps you decide which affected components matter most for your own software.

Quick check

Is this the same bug as CVE-2026-16927?

No. They are separate CVEs with different vectors, even though both are TOCTOU races and share a bulletin. One fix pack addresses both.

Sources

Last reviewed: 18 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.