# CVE-2026-55252: OpenRun: Redirect URL validation bypass using //host paths leads to Open Redirect

> Attackers can bypass redirect URL validation in OpenRun to perform open redirect attacks, potentially tricking users into visiting malicious sites.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-h5g6-xmh4-hc37, GO-2026-5956

## What is CVE-2026-55252?

CVE-2026-55252 is a medium-severity vulnerability in openrundev openrun, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

OpenRun is an open-source, self-hosted GitOps platform for deploying web apps and internal tools to Docker or Kubernetes. Prior to version 0.17.7, the restrictions on redirect URLs in openrun can be bypassed by attackers, leading to open redirect attacks. This issue has been patched in version 0.17.7.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

3 open source packages ship an affected version, including github.com/openrundev/openrun.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/openrundev/openrun` | Go | All versions | 0.17.7 |
| `github.com/openrundev/openrun` | Go | All versions | 0.17.7 |
| `github.com/openrundev/openrun` | Go | All versions | 0.17.7 |

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

Upgrade github.com/openrundev/openrun to 0.17.7 or later.

## Is CVE-2026-55252 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55252 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55252 is a medium-severity vulnerability in openrundev openrun, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55252 exists.

Affected packages and fixed versions:
- github.com/openrundev/openrun (Go): affected all versions; fixed in 0.17.7
- github.com/openrundev/openrun (Go): affected all versions; fixed in 0.17.7
- github.com/openrundev/openrun (Go): affected all versions; fixed in 0.17.7

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-55252/ (Markdown: https://insights.sbomify.com/CVE-2026-55252/index.md)
```

## Sources

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

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