CVE-2026-24810
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 · uneditedBuffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in rethinkdb (src/cjson modules). This vulnerability is associated with program files cJSON.Cc. This issue affects rethinkdb: through v2.4.4.
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 confidenceA classic buffer overflow vulnerability exists in the cJSON module of RethinkDB (cJSON.cc). The vulnerability stems from copying data into a buffer without proper size validation, potentially allowing an attacker to overwrite adjacent memory and execute arbitrary code.
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
- Y
- User interaction
- None
- Scope
- N
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:N/AU:Y/R:U/V:C/RE:M/U:Red
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 RethinkDB installation and versionRun 'rethinkdb --version' or check the installed package version using your system's package manager (dpkg -l | grep rethinkdb, rpm -qi rethinkdb, or brew list --versions rethinkdb)Affected if The installed version is 2.4.4 or lower, or if the version cannot be determined but RethinkDB is present
-
Locate the cJSON module fileSearch for cJSON.cc or cJSON related files in the RethinkDB installation directory, typically found under /usr/lib/rethinkdb or /opt/rethinkdb (find /usr -name 'cJSON*' 2>/dev/null)Affected if The cJSON.cc file exists in the RethinkDB installation directory, indicating the vulnerable component is present
-
Determine if cJSON functionality is in active useReview application logs, configuration files, or database queries that involve JSON parsing operations within RethinkDB; check for any custom scripts or integrations that use cJSON-based featuresAffected if RethinkDB is actively processing JSON data through its cJSON module (common in most RethinkDB deployments)
-
Check network exposure of RethinkDB serviceRun 'netstat -tlnp | grep rethinkdb' or 'ss -tlnp | grep rethinkdb' to identify listening ports, and review firewall rules (iptables -L or ufw status)Affected if RethinkDB is bound to a network interface accessible from untrusted networks (0.0.0.0 or external IP rather than 127.0.0.1)
A user is affected if RethinkDB version 2.4.4 or lower is installed, the cJSON module is present, and the database is processing JSON data, especially if exposed to network access.
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.
From vendor dataUpgrade RethinkDB to a patched version beyond v2.4.4. If immediate patching is not possible, restrict network access to the RethinkDB service and implement input validation at network boundaries.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24810 — 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-2026-24810 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