What is the CVSS score of CVE-2026-17617?

CVE-2026-17617 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.3%.

Which versions of IBM Application Gateway Operator are affected by CVE-2026-17617?

IBM Application Gateway Operator versions 22.2 through 26.06 contain a critical network isolation bypass vulnerability that could allow attackers to access sensitive internal services and cloud…. A patch is available.

How to fix or mitigate CVE-2026-17617?

Within 24 hours, identify all systems running IBM Application Gateway Operator versions 22.2 through 26.06 and assess their network exposure to untrusted sources and connectivity to internal services. Within 7 days, validate the available vendor patch in a non-production environment for compatibility with your current configuration and deployment topology. Within 30 days, deploy the patched version to all affected production systems to eliminate the network isolation bypass vector.

IBM Application Gateway Operator CVE-2026-17617

EUVD-2026-53450 CRITICAL

Server-Side Request Forgery (SSRF) (CWE-918)

2026-08-05 ibm

GHSA-g8h4-jvg2-r37q

SSRF IBM Application Gateway Operator

9.8

CVSS 3.1 · NVD

Severity by source

Vendor (ibm) PRIMARY

HIGH

qualitative

NVD

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

8.5 HIGH

SSRF via CR URL fields normally requires RBAC-gated CR write access (PR:L), crosses into internal networks (S:C), yields high confidentiality but limited integrity and no direct availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (ibm).

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Updated

Aug 10, 2026 - 17:58 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Aug 10, 2026 - 17:52 vuln.today

cvss_changed

Severity Changed

Aug 10, 2026 - 17:52 NVD

HIGH CRITICAL

CVSS changed

Aug 10, 2026 - 17:52 NVD

8.5 (HIGH) 9.8 (CRITICAL)

Analysis Generated

Aug 05, 2026 - 17:34 vuln.today

CVE Published

Aug 05, 2026 - 16:18 nvd

HIGH 8.5

DescriptionNVD

IBM Application Gateway Operator 22.2 through 26.06 is vulnerable to Server-Side Request Forgery (SSRF) due to insufficient validation of URLs specified in custom resources.

AnalysisAI

Server-Side Request Forgery in IBM Application Gateway Operator versions 22.2 through 26.06 lets remote unauthenticated attackers coerce the operator into issuing arbitrary HTTP requests by supplying attacker-controlled URLs in custom resources that the operator fails to validate. Because the operator typically runs inside a Kubernetes/OpenShift cluster, this SSRF can reach internal-only services and cloud metadata endpoints. There is no public exploit identified at time of analysis, EPSS risk is low (0.29%, 21st percentile), and CISA SSVC rates exploitation as none.

Technical ContextAI

IBM Application Gateway (IAG) Operator is a Kubernetes/OpenShift operator that provisions and manages IBM Application Gateway instances via Custom Resources (CRDs). The affected component is identified by CPE cpe:2.3:a:ibm:application_gateway_operator. The root cause is CWE-918 (Server-Side Request Forgery): the operator accepts URL values inside custom-resource specifications and dereferences or forwards requests to them without sufficient validation or allow-listing. In an operator pattern, the controller reconciles CR state from a privileged position within the cluster network, so an unvalidated URL becomes a request originated by a trusted in-cluster identity, potentially bypassing network segmentation that would otherwise block an external caller.

RemediationAI

Patch available per vendor advisory - upgrade the IBM Application Gateway Operator to the fixed release identified in IBM's advisory at https://www.ibm.com/support/pages/node/7282296 (the exact fixed version is not stated in the provided data, so confirm the target build directly from that advisory before upgrading). Until the operator is patched, restrict who can create or modify the operator's custom resources via Kubernetes RBAC so untrusted users cannot inject arbitrary URLs, and apply egress NetworkPolicies to the operator's namespace/pod to block outbound requests to internal service ranges, link-local addresses, and the cloud metadata endpoint (169.254.169.254) - noting this may break legitimate outbound integrations the operator relies on, so validate required destinations first. Also enable admission-controller validation on the CR fields carrying URLs to enforce an allow-list of expected hosts.