# CVE-2026-15639: Reflected Cross-Site Scripting

> Attackers can execute arbitrary JavaScript in victims' browsers via crafted links, potentially leading to session hijacking or data theft in Delinea Secret Server.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:H/SI:H/SA:H`)
- **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:** No
- **Published:** 15 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-5jwp-q2ph-6mgc

## What is CVE-2026-15639?

CVE-2026-15639 is a critical cross-site scripting vulnerability in Delinea Secret Server (On-Prem), published on 15 Sep 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

An attacker can craft a malicious link that, if used by a legitimate user, may cause the user's browser to run JavaScript supplied by the attacker.

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

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


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

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

## Is CVE-2026-15639 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15639 is a critical cross-site scripting vulnerability in Delinea Secret Server (On-Prem), published on 15 Sep 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: There is no known exploitation of CVE-2026-15639 in the wild and no public exploit code.

Affected product: Delinea Secret Server (On-Prem). 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-15639/ (Markdown: https://insights.sbomify.com/CVE-2026-15639/index.md)
```

## Sources

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

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