CVE-2026-17617 is a high severity server side request forgery flaw (CVSS 8.5) in IBM Application Gateway Operator versions 22.2 through 26.06. The operator does not sufficiently validate URLs given in custom resources. Check IBM's bulletin for the fixed version and update.
What's affected
Per the CVE record, IBM Application Gateway Operator 22.2 through 26.06 is affected. The record does not name a fixed version. IBM's support bulletin is the source for that.
How to check if you're exposed
If you run the operator on Kubernetes or OpenShift, list the installed operator version and compare it with the range above. In a cluster, you can also list who may create or edit the custom resources the operator reads, since the flaw involves URLs set there.
kubectl get customresourcedefinitions | grep -i ibm
The command only shows which IBM related definitions exist. Confirm the operator version through your operator catalog or deployment.
Safeguard's free dependency scan at gold.safeguard.sh/scan reads manifests and lock files, so it will not see device firmware or an installed appliance. Use it for the application dependencies around this product, and use the vendor's own version check for the product itself.
What to do now
- Find every cluster where the operator is installed.
- Read IBM's bulletin and upgrade to the fixed release it names.
- Limit who can create or modify the operator's custom resources to trusted administrators.
- Check egress network policy so the operator cannot reach internal services it does not need.
Why it matters
Server side request forgery, CWE-918, means a service can be tricked into making a request to a destination the attacker picks. The usual damage is reaching internal systems or metadata services that are not exposed to the outside. Here the CVSS vector has a changed scope and high confidentiality impact, which fits that pattern.
The attack needs a low privilege account, because the unsafe URLs come from custom resources. That makes tight access control on those resources a useful second layer. The CVE is not in CISA's KEV list.
Quick check
Who can trigger it?
The record gives a low privilege requirement and a network vector. Anyone who can set URLs in the custom resources is the practical concern.
Does an egress policy fix it?
It limits the damage but does not replace the update.
Sources
Last reviewed: 19 October 2026.
