dbcve.org
KvrocksApplication · Apache

CVE-2025-59790

MEDIUM · 5.4 CVSS v3.1 Published 2025-11-28
Fix available
A fix is available. Upgrade to 2.14.0 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Improper Privilege Management vulnerability in Apache Kvrocks. This issue affects Apache Kvrocks: from v2.9.0 through v2.13.0. Users are recommended to upgrade to version 2.14.0, which fixes the issue.

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 · moderate confidence

Improper Privilege Management vulnerability in Apache Kvrocks allows unauthorized privilege escalation or privilege misuse in versions 2.9.0 through 2.13.0. The specific nature of the privilege management flaw is not detailed in the advisory, but the medium severity CVSS score suggests limited scope of impact.

MitigationUpgrade Apache Kvrocks to version 2.14.0 which contains the fix for this improper privilege management issue.

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
KvrocksApplication
Affected:>= 2.9.0, < 2.14.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Check Apache Kvrocks server version
    Run `kvrocks --version` from the command line, or connect to the Kvrocks instance and execute the `INFO server` command via redis-cli to retrieve the version field
    Affected if The reported version falls within the range 2.9.0 through 2.13.0 (e.g., 2.9.0, 2.10.5, 2.13.0)
  2. Verify running executable path
    Locate the kvrocks binary in use: `which kvrocks` or `ps aux | grep kvrocks` to identify the exact executable serving the instance
    Affected if The executable version (as shown by `--version`) matches the affected version range
  3. Check server startup script or container image version
    Inspect the startup script, systemd service file, or Docker/Kubernetes image tag that launches kvrocks (e.g., `cat /etc/systemd/system/kvrocks.service` or `docker images | grep kvrocks`)
    Affected if The script references or the image tag corresponds to a version between 2.9.0 and 2.13.0
  4. Inspect configuration for ACL or user privilege settings
    Review kvrocks.conf for `acl` or `user` directives, or run `ACL LIST` command if ACL is enabled, to understand the privilege model in use
    Affected if ACL or user privilege features are configured on a version within the affected range (the vulnerability involves improper privilege management in these configurations)

You are affected if the installed Apache Kvrocks version is 2.9.0, 2.10.x, 2.11.x, 2.12.x, or 2.13.0; upgrade to 2.14.0 or later to resolve this improper privilege management issue.

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 2.14.0 or later
Fixed in 2.14.0
Interim mitigation

Upgrade Apache Kvrocks to version 2.14.0 which contains the fix for this improper privilege management issue.

Recommended fix High confidence

2.14.0

  1. Backup all Kvrocks data and configuration files before upgrading
  2. Stop the Kvrocks service to prevent data corruption during upgrade
  3. Download Kvrocks version 2.14.0 from the official Apache Kvrocks releases repository (e.g., GitHub apache/kvrocks)
  4. Install the new version following standard installation procedures for your operating system
  5. Verify the integrity of the downloaded package using checksums if available
  6. Restore any custom configuration settings from the backup to the new installation
  7. Start the Kvrocks service and verify it runs without errors
  8. Confirm the installed version is 2.14.0 by checking kvrocks --version or querying the server

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

Fix this in Kvrocks 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 the upgrade done

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-59790 — 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-59790 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