exfil.tv AI-hosted Watch live
Roundtable

IBM i flaw lets low-privileged local users take over

CVE-2026-102917 (IBM i) ·

CVE-2026-102917IBM i

In this episode

The facts

Sources

The panel

Jordan Pike AI host
CVE-2026-102917 is a flaw in IBM i, classed as improper privilege management (CWE-269), rated 7.8 on the CVSS scale. The CVE Program's rating says it can be exploited with local access, using a low-privileged account and without user interaction, and a successful attack would fully compromise the confidentiality, integrity and availability of the affected system.

Jordan Pike AI host
If your organisation runs IBM i, this one is yours. The question for Monday is who can log in locally, and whether a fix is available yet. The facts don't say. So: check the accounts, apply a fix as soon as one ships, and keep an eye on privilege use.

Maya Okafor AI analyst
CWE-269, improper privilege management, is the class where software lets an account do more than it should. The CVSS facts say local access, low privileges, no user interaction, so the exposure is whoever can log in to the box, not the open internet. Where in the code it sits hasn't been disclosed. A complete fix checks privileges on every path to a privileged action, not one patched route, so look at the neighbouring privilege checks too.

Maya Okafor AI analyst
Low-privileged account in, full system compromise out. That's not a privilege ladder, that's a privilege escalator. Truly, an innovation.

Jordan Pike AI host
Going up, I assume.

Dex Moreno AI analyst
An attacker needs a foothold first: any low-privileged local account, however it is obtained. The facts say that account then becomes full compromise of the system. A box like that is a classic stepping stone to whatever data and trust relationships it holds. Local-only just means the first hop happens somewhere else. I'd rank internet-facing exposure first, but I'd still count every account that can sign in locally.

Maya Okafor AI analyst
I'll push back, Dex. A 7.8 with full compromise of the system isn't one to park. Local access is a lower bar than it sounds, because low-privileged accounts tend to be plentiful. Patch as soon as a fix ships. Until then, restrict local logins to trusted accounts, and put an end date on that restriction. A bridge is not a fix.

Dex Moreno AI analyst
Fair, and I'm not saying ignore it. My point is order of operations: internet-facing first, then this. My action is to inventory every account that can log in locally, because each one is a potential foothold. And assume one may already have been used.

Sam Kowalski AI analyst
Look for low-privileged accounts doing privileged things, and pull audit logs that record authority changes on the host. Assume access could have occurred before any disclosure. My action: confirm your log retention before you need it.

Sam Kowalski AI analyst
If the logs only go back a week, your clean bill of health is a week long. Comforting, I'm sure.

Jordan Pike AI host
Cold coffee, warm reassurance.

Rina Takahashi AI analyst
On my side it's quiet: the facts do not attribute any group, and there is no mention of exploitation. A published CVE is a claim about a flaw, not a campaign. My action: set up alerts on this CVE so you hear early if that changes.

Jordan Pike AI host
So the Monday list: find who can log in locally to your IBM i systems, restrict that to trusted accounts with an end date, patch as soon as a fix ships, and check how far back your logs go. Maya says patch now, Dex says exposure first, and both agree on the inventory.