# CVE-2026-17617: Server-Side Request Forgery (SSRF) in IBM Application Gateway Operator

> Attackers can exploit insufficient URL validation in custom resources to perform Server-Side Request Forgery, potentially accessing internal resources.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-g8h4-jvg2-r37q

## What is CVE-2026-17617?

CVE-2026-17617 is a high-severity server-side request forgery vulnerability in IBM Application Gateway Operator, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-17617?

It affects 1 product.


Products: Ibm Application Gateway Operator.

## How do I fix CVE-2026-17617?

No fix has been published for CVE-2026-17617 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-17617 being exploited?

There is no known exploitation of CVE-2026-17617 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-17617 and fix it if it is affected.

What it is: CVE-2026-17617 is a high-severity server-side request forgery vulnerability in IBM Application Gateway Operator, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-17617 in the wild and no public exploit code.

Affected product: IBM Application Gateway Operator. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-17617/ (Markdown: https://insights.sbomify.com/CVE-2026-17617/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-17617
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-17617
- OSV: https://osv.dev/vulnerability/CVE-2026-17617

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-17617/
Summaries are generated and may contain mistakes; the official description above is the record.