# CVE-2025-1695: NGINX Unit Java Vulnerability

> Remote attackers can trigger an infinite loop in the Java module, causing high CPU usage and limited denial of service.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/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:** 4 Mar 2025
- **Updated:** 4 Mar 2025
- **Also known as:** BIT-nginx-2025-1695, GHSA-7w3m-9pfq-8m82

## What is CVE-2025-1695?

CVE-2025-1695 is a medium-severity denial of service vulnerability in F5 NGINX Unit, published on 4 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In NGINX Unit before version 1.34.2 with the Java Language Module in use, undisclosed requests can lead to an infinite loop and cause an increase in CPU resource utilization.  This vulnerability allows a remote attacker to cause a degradation that can lead to a limited denial-of-service (DoS).  There is no control plane exposure; this is a data plane issue only.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

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

1 open source package ship an affected version, including nginx. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nginx` | Bitnami | From 1.29.1 | None |

Products: F5 Nginx Unit.

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

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

## Is CVE-2025-1695 being exploited?

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

## Other vulnerabilities in F5 NGINX Unit

- [CVE-2019-7401](https://insights.sbomify.com/CVE-2019-7401/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1695 is a medium-severity denial of service vulnerability in F5 NGINX Unit, published on 4 Mar 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-1695 in the wild and no public exploit code.

Affected packages and fixed versions:
- nginx (Bitnami): affected from 1.29.1; no fix listed

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-1695/ (Markdown: https://insights.sbomify.com/CVE-2025-1695/index.md)
```

## Sources

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

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