# CVE-2025-59978: Junos Space: Stored cross-site scripting vulnerability in web application

> Attackers can inject scripts into Junos Space web pages to execute commands with administrative privileges when viewed by other users.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/R:U/RE:M`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Oct 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-2hw3-rfjc-q8m6

## What is CVE-2025-59978?

CVE-2025-59978 is a critical cross-site scripting vulnerability in Juniper Junos Space, published on 9 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

An Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Juniper Networks Junos Space allows an attacker to store script tags directly in web pages that, when viewed by another user, enable the attacker to execute commands with the target's administrative permissions.
This issue affects all versions of Junos Space before 24.1R4.

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

## Which versions are affected by CVE-2025-59978?

It affects 1 product.


Products: Juniper Junos Space.

## How do I fix CVE-2025-59978?

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

## Is CVE-2025-59978 being exploited?

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

## Other vulnerabilities in Juniper Junos Space

- [CVE-2014-3412](https://insights.sbomify.com/CVE-2014-3412/): Command injection in n/a (critical 10.0)
- [CVE-2014-3413](https://insights.sbomify.com/CVE-2014-3413/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2016-1265](https://insights.sbomify.com/CVE-2016-1265/): Junos Space: privilege escalation vulnerabilities in Junos Space (critical 9.8)
- [CVE-2017-10622](https://insights.sbomify.com/CVE-2017-10622/): Junos Space: Authentication bypass vulnerability (critical 9.8)
- [CVE-2016-4926](https://insights.sbomify.com/CVE-2016-4926/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59978 and fix it if it is affected.

What it is: CVE-2025-59978 is a critical cross-site scripting vulnerability in Juniper Junos Space, published on 9 Oct 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-59978 in the wild and no public exploit code.

Affected product: Juniper Junos Space. 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-2025-59978/ (Markdown: https://insights.sbomify.com/CVE-2025-59978/index.md)
```

## Sources

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

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