KvrocksApplication · Apache
CVE-2025-26413
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 · uneditedImproper Input Validation vulnerability in Apache Kvrocks. The SETRANGE command didn't check if the `offset` input is a positive integer and use it as an index of a string. So it will cause the server to crash due to its index is out of range. This issue affects Apache Kvrocks: through 2.11.1. Users are recommended to upgrade to version 2.12.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 · high confidenceThe SETRANGE command in Apache Kvrocks fails to validate that the offset parameter is a positive integer before using it as a string index. When invalid (negative or out-of-range) offset values are provided, the server crashes due to an out-of-bounds array access. This affects versions through 2.11.1.
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
< 2.12.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Kvrocks installation versionRun `kvrocks --version` or check the version banner on server startup, or query the server with `INFO server` commandAffected if The reported version is any version below 2.12.0 (including 2.11.1 and earlier)
-
Verify SETRANGE command availabilityConfirm the SETRANGE command is accessible in the deployment - this is a built-in command in Kvrocks and is available by default in standard configurationsAffected if SETRANGE command is enabled and accessible (default state in unhardened configurations)
-
Confirm server exposureAssess whether the Kvrocks port (default 6666) is reachable from untrusted networks or if the server accepts connections from untrusted clientsAffected if The Kvrocks server accepts network connections from untrusted sources without additional access controls
You are affected if your deployed Kvrocks version is any release prior to 2.12.0 and the SETRANGE command is accessible to your clients or users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.12.0
Upgrade Apache Kvrocks to version 2.12.0 or later which includes proper input validation for the SETRANGE offset parameter.
2.12.0
- 1. Back up your Kvrocks data and configuration files
- 2. Stop the Kvrocks server
- 3. Download Apache Kvrocks version 2.12.0 from the official Apache Kvrocks release repository or package manager
- 4. Install the new version following your deployment method (compilation or package installation)
- 5. Verify the installation by running kvrocks --version
- 6. Start the Kvrocks server with the updated binary
- 7. Test that the SETRANGE command now properly validates offset as a positive integer
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
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 locallyCheck whether your project pulls in CVE-2025-26413 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26413 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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