# CVE-2025-59975: Junos Space: Flooding device with inbound API calls leads to WebUI and CLI management access DoS

> Unauthenticated attackers can cause a denial of service in Junos Space by flooding API calls, blocking management access until a reboot.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:Y/R:U/V:C/RE:M`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2025
- **Updated:** 9 Oct 2025
- **Also known as:** GHSA-834q-vmvq-2qjx

## What is CVE-2025-59975?

CVE-2025-59975 is a high-severity denial of service vulnerability in Juniper Junos Space, published on 9 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Uncontrolled Resource Consumption vulnerability in the HTTP daemon (httpd) of Juniper Networks Junos Space allows an unauthenticated network-based attacker flooding the device with inbound API calls to consume all resources on the system, leading to a Denial of Service (DoS).

After continuously flooding the system with inbound connection requests, all available file handles become consumed, blocking access to the system via SSH and the web user interface (WebUI), resulting in a management interface DoS. A manual reboot of the system is required to restore functionality.

This issue affects Junos Space: 
  *  all versions before 22.2R1 Patch V3, 
  *  from 23.1 before 23.1R1 Patch V3.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Juniper Junos Space.

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

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

## Is CVE-2025-59975 being exploited?

There is no known exploitation of CVE-2025-59975 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-59975 and fix it if it is affected.

What it is: CVE-2025-59975 is a high-severity denial of service vulnerability in Juniper Junos Space, published on 9 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59975 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-59975/ (Markdown: https://insights.sbomify.com/CVE-2025-59975/index.md)
```

## Sources

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

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