dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2026-46752

CRITICAL · 10.0 CVSS v4.0 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

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
Redis Lua HEAP overflow in cjson library vulnerability in Apache Kvrocks. This issue affects Apache Kvrocks: from 2.0.4 through 2.15.0. Users are recommended to upgrade to version 2.16.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

Heap overflow vulnerability in the cjson Lua library within Apache Kvrocks allows remote attackers to execute arbitrary code through specially crafted Lua scripts that trigger memory corruption during JSON encoding/decoding operations.

MitigationUpgrade Apache Kvrocks to version 2.16.0 or later. If immediate patching is not feasible, restrict network access to Kvrocks instances and consider disabling Lua scripting as a compensating control.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 installed Apache Kvrocks version
    Run 'kvrocks --version' or check the package version installed via your package manager (e.g., 'rpm -q kvrocks', 'dpkg -l kvrocks', or 'kvrocks -v' from the binary)
    Affected if Version is lower than 2.16.0 (the fixed release)
  2. Verify Lua scripting is enabled
    Check the Kvrocks configuration file (typically kvrocks.conf) for the 'lua' or 'enable-command-script' directive, or run 'CONFIG GET lua' via redis-cli if the server is running
    Affected if Lua scripting is enabled (lua-enabled setting is true or not set to false)
  3. Confirm cjson library is available or loaded
    Connect to Kvrocks via redis-cli and run 'EVAL "local cjson = require('cjson'); return 'ok'" 0' to test if cjson module loads
    Affected if cjson module loads successfully without error
  4. Assess network exposure
    Review firewall rules, bind address in kvrocks.conf (parameter 'bind'), and network ACLs to determine if the Kvrocks port is accessible from untrusted networks
    Affected if Kvrocks port (default 6666) is exposed to untrusted or public networks without authentication or network filtering

Environment is affected if running Kvrocks version below 2.16.0 with Lua scripting enabled, cjson library loaded, and the instance is network-accessible to remote attackers.

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 Apache Kvrocks to version 2.16.0 or later. If immediate patching is not feasible, restrict network access to Kvrocks instances and consider disabling Lua scripting as a compensating control.

Recommended fix High confidence

2.16.0

  1. 1. Back up your current Kvrocks data and configuration files
  2. 2. Check your current Kvrocks version using `kvrocks --version` to confirm it's between 2.0.4 and 2.15.0
  3. 3. Download Kvrocks version 2.16.0 from the official Apache Kvrocks releases (e.g., GitHub apache/kvrocks)
  4. 4. Stop the running Kvrocks service
  5. 5. Install the new version (via package manager, binary, or compile from source depending on your deployment method)
  6. 6. Verify the upgrade was successful by running `kvrocks --version` and confirming it shows 2.16.0
  7. 7. Start the Kvrocks service and verify normal operation
  8. 8. Monitor logs for any unusual errors post-upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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