Skip to content
Weekly Signal
Live intelligence Updated 21 Aug 2026 · 22:12 UTC

IBM · I

CVE-2026-17101

IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker to execute arbitrary code or obtain sensitive information due to improper authentication.

Recommended action

Handle this through the normal risk-based patching cycle while monitoring for change. IBM Security advisory 7283292

View response plan
CVSS9.6
EPSS0.4%
KEVNo
ExploitationNone
RemediationNot yet verified ↓

Assessment

Why it matters

EPSS is 0.4%; technical severity is CVSS 9.6.

IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote attacker to execute arbitrary code or obtain sensitive information due to improper authentication.

Who should care

  • Teams operating I
  • Vulnerability and exposure management teams
  • Security operations teams monitoring exploitation activity

Response plan

What I would do

  1. Confirm whether I is present in the environment.
  2. Identify affected versions and establish whether vulnerable services are exposed or reachable.
  3. IBM Security advisory 7283292
  4. Review relevant security telemetry for evidence of attempted or successful exploitation.
  5. Document the remediation decision and track it to verified completion.

Treatment intelligence

Remediation intelligence

Not yet verified

Vendor sources are listed before government and third-party guidance. Confirm product applicability and change prerequisites before deployment.

Verification noteAutomated link verification has not completed for this guidance yet.

Technical details

CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CWE
CWE-287
Affected versions
IBM I (Version 7.3 | Version 7.4 | Version 7.5 | Version 7.6)
Fixed versions
No explicit fixed version is currently recorded.
Published
13 August 2026
Attack vector
Network
Privileges required
None
User interaction
Required

Signal timeline

  1. CVE published
  2. Latest EPSS score: 0.4%
  3. Signal calculated at 14
Live public intelligence This assessment combines public-source evidence. Validate the affected product, version and exposure against your own environment before making a risk decision.