IBM i EUVD-2026-58404

No authentication is required - the CVSS vector PR:N/UI:N confirms unauthenticated remote exploitation with no user interaction needed. The attack vector is network (AV:N) with low complexity (AC:L), meaning the vulnerable service must be network-reachable from the attacker. The primary limiting factor is that IBM i systems are typically deployed in controlled enterprise environments with network segmentation, reducing exposure compared to internet-facing systems. The specific network service, protocol, or port that exposes the vulnerable code path is not identified in the available data; defenders cannot confirm whether default IBM i configurations expose this path or whether it requires a specific licensed program or service to be active.

The CVSS 8.2 HIGH score is driven by a fully unauthenticated, network-accessible, low-complexity attack path (AV:N/AC:L/PR:N/UI:N) with high availability impact - a combination that warrants serious attention in any environment running IBM i. The slight integrity impact (I:L) alongside the primary DoS outcome suggests the out-of-bounds write may corrupt adjacent state in addition to crashing the service. No EPSS score was provided in the source data, so exploitation probability cannot be quantified; however, the absence of KEV listing and public POC code moderates the urgency relative to the raw CVSS score. IBM i systems tend to be deeply embedded in business-critical workflows - payroll, ERP, supply chain - meaning even a transient availability disruption carries significant operational consequence. Any mid-sized enterprise or government shop running IBM i, whether in a large city or a regional office like one in ustka, should treat this as a priority patching item given the unauthenticated network vector, even in the absence of confirmed active exploitation. The primary uncertainty is the specific network service affected: without knowing which daemon or protocol exposes the vulnerable code path, defenders cannot apply targeted network-layer controls as a compensating measure.

A remote unauthenticated attacker sends a specially crafted network request to an IBM i system running a vulnerable release (7.3-7.6), triggering an out-of-bounds write in the target service's buffer handling code. The write corrupts adjacent memory, causing the affected component to crash and rendering it unavailable - potentially taking down dependent business processes. No public proof-of-concept code has been identified, but the low attack complexity (AC:L) and absence of authentication requirements mean a working exploit would be straightforward to develop by a capable threat actor.