CVE-2026-16967 is a Time-of-Check-Time-of-Use (TOCTOU) vulnerability in IBM i involving symbolic link manipulation during filesystem operations. The vulnerability carries a CVSS 8.5 rating, but the severity metric undersells the actual risk in IBM i environments. The 'authenticated attacker' qualifier is technically accurate but functionally broad — IBM i's definition of 'authenticated' includes service accounts, batch job contexts, and QTMHHTTP service accounts that run middleware with object authorities far exceeding typical user permissions. An attacker who wins the race window doesn't merely gain a foothold; they redirect a privileged filesystem operation into an unintended target within the OS/400 object namespace, potentially reaching integrated database objects, spooled files, or program objects that carry their own permission grants. The severity amplification stems from IBM i's object-level authority model: both the 'check' and 'use' phases execute inside a process context with permissions granted at the object level — often through group memberships like ALLOBJ or SECADM — that are entirely decoupled from the user who initiated the operation. This is categorically different from POSIX systems, where root-owned processes at least verify ownership before following symlinks. On IBM i, the attacker only needs to win the race, not escalate their own account privileges. The vulnerability affects IBM i 7.3 through 7.6, meaning multiple release trains are simultaneously exposed, and patch deployment in IBM i environments typically lags by months due to the operational complexity of testing business-critical workloads. Organizations should prioritize service account hygiene as an immediate mitigation — reviewing which accounts have object existence authority and whether the affected code paths can run under reduced privileges. The broader question is how many other TOCTOU patterns persist in this codebase: IBM i has shipped similar symbolic link race conditions in prior CVEs, suggesting the remediation has been transactional rather than architectural. A systematic audit for concurrent filesystem assumptions across the middleware layer is warranted.
CVE-2026-16967
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to gain unauthorized access to system objects due to a time-of-check to time-of-use (TOCTOU) race condition involving symbolic links.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisA detailed technical summary for this CVE is being prepared.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.3= 7.4= 7.5= 7.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThere is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $4,900. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-16967 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesCVE-2026-16967 is a Time-of-Check-Time-of-Use (TOCTOU) vulnerability in IBM i involving symbolic link manipulation during filesystem operations. The vulnerability carries a CVSS 8.5 rating, but the severity metric undersells the actual risk in IBM i environments. The 'authenticated attacker' qualifier is technically accurate but functionally broad — IBM i's definition of 'authenticated' includes service accounts, batch job contexts, and QTMHHTTP service accounts that run middleware with object authorities far exceeding typical user permissions. An attacker who wins the race window doesn't merely gain a foothold; they redirect a privileged filesystem operation into an unintended target within the OS/400 object namespace, potentially reaching integrated database objects, spooled files, or program objects that carry their own permission grants. The severity amplification stems from IBM i's object-level authority model: both the 'check' and 'use' phases execute inside a process context with permissions granted at the object level — often through group memberships like *ALLOBJ or *SECADM — that are entirely decoupled from the user who initiated the operation. This is categorically different from POSIX systems, where root-owned processes at least verify ownership before following symlinks. On IBM i, the attacker only needs to win the race, not escalate their own account privileges. The vulnerability affects IBM i 7.3 through 7.6, meaning multiple release trains are simultaneously exposed, and patch deployment in IBM i environments typically lags by months due to the operational complexity of testing business-critical workloads. Organizations should prioritize service account hygiene as an immediate mitigation — reviewing which accounts have object existence authority and whether the affected code paths can run under reduced privileges. The broader question is how many other TOCTOU patterns persist in this codebase: IBM i has shipped similar symbolic link race conditions in prior CVEs, suggesting the remediation has been transactional rather than architectural. A systematic audit for concurrent filesystem assumptions across the middleware layer is warranted.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-16967 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data