IBM ACS CVE-2026-13433

Exploitation requires that IBM i Access Client Solutions be explicitly configured to update its product code from an IBM i host - this is the concrete, non-default prerequisite named in the description ('when configured to update from an IBM i'). The attacker must also occupy a delivery position for that update: either control of the IBM i update host or a man-in-the-middle on the adjacent network (consistent with the CVSS AV:A adjacent vector). Limiting factors: clients that install/update ACS by other means are not exposed; the attacker cannot exploit purely from an arbitrary remote internet location (adjacent, not network-wide); and the attack depends on an ACS update actually being triggered. Per CVSS the flaw needs no user interaction (UI:N) and no prior privileges on the client (PR:N), but the required update-injection position makes it materially harder than the AC:L rating implies.

Signals here conflict in an instructive way. The CVSS base score is 9.6 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) - near-critical, driven by scope change and total CIA impact - yet EPSS is only 0.11% (1st percentile) and CISA's SSVC decision records Exploitation: none and Automatable: no, with Technical Impact: total. In other words, IF exploited the impact is complete workstation compromise, but exploitation is neither observed nor easily automated. The vendor vector rates AC:L and PR:N, but realistic exploitation requires the attacker to occupy a privileged delivery position (a compromised IBM i update host or a man-in-the-middle on the adjacent network), which is better modeled as higher attack complexity - verify the AC:L rating against the practical requirement to inject code into the update stream. There is no CISA KEV listing and no public POC. Net assessment: a genuinely serious integrity flaw for IBM i shops that enable server-hosted ACS updates, but current real-world urgency is moderate rather than emergency - patch on a normal-to-expedited cycle rather than treating it as actively exploited.

An attacker who has compromised an IBM i server used for ACS updates, or who can man-in-the-middle the update channel on the adjacent network, replaces the legitimate ACS product code with a malicious build. When an ACS client configured to update from that IBM i performs its next update, it downloads and runs the tampered code without integrity verification, giving the attacker arbitrary code execution on the user's workstation. No public exploit is identified at time of analysis, and the adjacent-network positioning requirement raises the practical bar.