dbcve.org
Nginx UnitWeb server / proxy · F5

CVE-2025-1695

MEDIUM · 5.3 CVSS v3.1 Published 2025-03-04
Fix available
A fix is available. Upgrade to 1.34.2 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In NGINX Unit versions prior to 1.34.2 with the Java Language Module enabled, an attacker can send specific requests that trigger an infinite loop in the data plane, causing excessive CPU consumption and a limited denial-of-service condition.

MitigationUpgrade NGINX Unit to version 1.34.2 or later. Since this is a data plane issue, ensure the Java Language Module is also updated to the compatible version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nginx UnitWeb server / proxy
Affected:>= 1.29.1, < 1.34.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine NGINX Unit version
    Query the NGINX Unit control API endpoint (typically via curl to localhost on port 8080 or the configured control socket) using the GET /status endpoint, or run 'unitd --version' if you have CLI access. The version is returned in the JSON response under the 'version' field.
    Affected if The installed version is 1.29.1, 1.30.0, 1.31.0, 1.32.0, 1.33.0, or 1.34.0 (any version from 1.29.1 through 1.34.0 inclusive, but not 1.34.2 or later).
  2. Verify Java Language Module is loaded
    Query the NGINX Unit control API using GET /config/modules endpoint or inspect the running configuration via GET /config. Look for the 'java' module entry in the modules list.
    Affected if The Java Language Module appears in the loaded modules configuration, meaning it is enabled and active.
  3. Confirm Java application routing exists
    Query the NGINX Unit control API GET /config/routes endpoint or examine the overall configuration to see if any routes direct traffic to Java language handlers (check for 'language' set to 'java' in listener or route configurations).
    Affected if There are active routes or listeners configured to process requests using the Java language module.

You are affected if NGINX Unit version is 1.29.1 or higher but below 1.34.2 AND the Java Language Module is loaded and actively routing requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.34.2 or later
Fixed in 1.34.2
Interim mitigation

Upgrade NGINX Unit to version 1.34.2 or later. Since this is a data plane issue, ensure the Java Language Module is also updated to the compatible version.

Recommended fix High confidence

1.34.2 or later

  1. Identify current NGINX Unit version using `unitd --version` or similar
  2. Stop the NGINX Unit service
  3. Upgrade NGINX Unit to version 1.34.2 or later
  4. Verify the upgrade was successful by checking the version
  5. Restart the NGINX Unit service
  6. If Java Language Module is in use, verify configuration is intact

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nginx Unit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1695 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1695 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data