dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2025-60536

HIGH · 7.5 CVSS v3.1 Published 2025-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
An issue in the Configure New Cluster interface of kafka-ui v0.6.0 to v0.7.2 allows attackers to cause a Denial of Service (DoS) via uploading a crafted configuration file.

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

A vulnerability in kafka-ui versions 0.6.0 through 0.7.2 allows attackers to cause denial of service by uploading a specially crafted configuration file through the Configure New Cluster interface. The application fails to properly validate or sanitize configuration file content, leading to resource exhaustion or application crash.

MitigationUpgrade kafka-ui to a version newer than v0.7.2. If immediate upgrading is not possible, restrict access to the Configure New Cluster interface to trusted users only.

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

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
High

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

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. Identify kafka-ui version
    Locate the installed kafka-ui version by inspecting the application startup logs, the UI footer, the JAR/WAR file name, or the Docker image tag if running in a container. Compare the version number against the affected range 0.6.0 through 0.7.2.
    Affected if The installed version falls between 0.6.0 and 0.7.2 inclusive.
  2. Confirm Configure New Cluster feature is accessible
    Determine whether the Configure New Cluster interface is available in the kafka-ui deployment. This may require checking if the feature is exposed via the web UI, API endpoint, or configuration setting.
    Affected if The Configure New Cluster interface is present and accessible in the environment.
  3. Check for recent configuration upload activity
    Review application logs for any recent POST or upload requests targeting cluster configuration endpoints, especially large or malformed configuration file uploads that may indicate exploitation attempts.
    Affected if There are logs or evidence of configuration file uploads to the Configure New Cluster interface.
  4. Assess application availability
    Monitor the kafka-ui application for signs of degradation, crashes, or elevated resource consumption (CPU, memory, disk) that may indicate successful exploitation of the vulnerability.
    Affected if The application exhibits symptoms of resource exhaustion or unexpected termination.

A user is affected if kafka-ui version is between 0.6.0 and 0.7.2 inclusive AND the Configure New Cluster interface is accessible and has been used, or the application shows denial of service symptoms.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade kafka-ui to a version newer than v0.7.2. If immediate upgrading is not possible, restrict access to the Configure New Cluster interface to trusted users only.

Recommended fix High confidence

kafka-ui v0.7.3 or later

  1. Check the kafka-ui GitHub releases page for the latest available version (v0.7.3 or later)
  2. Backup your current kafka-ui configuration and data
  3. Stop the running kafka-ui instance
  4. Download and install the fixed kafka-ui release
  5. Restore your configuration
  6. Restart kafka-ui and verify the application is functioning normally
  7. Test that the Configure New Cluster interface handles configuration files correctly
Caveat Review release notes for any configuration format changes or migration requirements between v0.6.0-v0.7.2 and the target version

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60536 — 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-60536 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