# CVE-2026-78415: IBM Sterling Secure Proxy is vulnerable to multiple issues

> Remote authenticated attackers can perform UI spoofing and phishing attacks via improper neutralization of user-supplied HTML markup in IBM Sterling Secure Proxy.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 14 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-4m7p-rm8x-7p4r

## What is CVE-2026-78415?

CVE-2026-78415 is a medium-severity cross-site scripting vulnerability in IBM Sterling Secure Proxy, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Sterling Secure Proxy 6.2.0.0 through 6.2.1.2 could allow a remote authenticated attacker to perform UI spoofing and phishing attacks due to improper neutralization of user-supplied HTML markup.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-78415 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78415 is a medium-severity cross-site scripting vulnerability in IBM Sterling Secure Proxy, published on 14 Sep 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-78415 in the wild and no public exploit code.

Affected product: IBM Sterling Secure Proxy. 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-78415/ (Markdown: https://insights.sbomify.com/CVE-2026-78415/index.md)
```

## Sources

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

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