# CVE-2025-52985: Security feature bypass in Junos OS Evolved

> Attackers can bypass firewall filters on Junos OS Evolved if prefix lists exceed ten entries, allowing unauthorized access to management interfaces.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2025
- **Updated:** 18 Jul 2025
- **Also known as:** GHSA-c7mr-h37w-h53j

## What is CVE-2025-52985?

CVE-2025-52985 is a medium-severity vulnerability in Juniper Junos Os Evolved, published on 11 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Use of Incorrect Operator

vulnerability in the Routing Engine firewall of Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to bypass security restrictions.

When a firewall filter which is applied to the lo0 or re:mgmt interface references a prefix list with 'from prefix-list', and that prefix list contains more than 10 entries, the prefix list doesn't match and packets destined to or from the local device are not filtered.

This issue affects firewall filters applied to the re:mgmt interfaces as input and output, but only affects firewall filters applied to the lo0 interface as output.
This issue is applicable to IPv4 and IPv6 as a prefix list can contain IPv4 and IPv6 prefixes.
This issue affects Junos OS Evolved:

  *  23.2R2-S3-EVO versions before 23.2R2-S4-EVO,
  *  23.4R2-S3-EVO versions before 23.4R2-S5-EVO,
  *  24.2R2-EVO versions before 24.2R2-S1-EVO,
  *  24.4-EVO versions before 24.4R1-S3-EVO, 24.4R2-EVO.

This issue doesn't affect Junos OS Evolved versions before 23.2R1-EVO.

Weakness: CWE-480 (Use of Incorrect Operator)

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

It affects 1 product.


Products: Juniper Junos Os Evolved.

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

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

## Is CVE-2025-52985 being exploited?

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

## Other vulnerabilities in Juniper Junos Os Evolved

- [CVE-2026-21902](https://insights.sbomify.com/CVE-2026-21902/): Junos OS Evolved: PTX Series: A vulnerability allows a unauthenticated, network-based attacker to execute code as root (critical 9.3)
- [CVE-2023-28983](https://insights.sbomify.com/CVE-2023-28983/): Junos OS Evolved: Shell Injection vulnerability in the gNOI server (high 8.8)
- [CVE-2025-21599](https://insights.sbomify.com/CVE-2025-21599/): Denial of service in Junos OS Evolved (high 8.7)
- [CVE-2024-47502](https://insights.sbomify.com/CVE-2024-47502/): Junos OS Evolved: TCP session state is not always cleared on the Routing Engine leading to DoS (high 8.7)
- [CVE-2024-39531](https://insights.sbomify.com/CVE-2024-39531/): Junos OS Evolved: ACX 7000 Series: Protocol specific DDoS configuration affects other protocols (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52985 is a medium-severity vulnerability in Juniper Junos Os Evolved, published on 11 Jul 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-52985 in the wild and no public exploit code.

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

## Sources

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

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