LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24810: A buffer overflow in rethinkdb/rethinkdb

Buffer 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.

CriticalCVSS 10Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

RethinkDB has a critical buffer overflow in its cJSON handling code. The public record says versions through 2.4.4 are affected. Because the CVSS score is 10.0 and the vector indicates network attack without authentication or user interaction, organizations running RethinkDB should treat this as urgent.

Executive priority

High priority. If RethinkDB is in use, assign immediate ownership to inventory, exposure reduction, and patch planning. The business risk is highest for internet-accessible or broadly reachable database deployments.

Technical view

CVE-2026-24810 is a CWE-120 classic buffer overflow in RethinkDB src/cjson modules, associated with cJSON.Cc. The CVE record lists RethinkDB through v2.4.4 as affected and assigns CVSS 4.0 score 10.0 with network, low-complexity, no-privilege, no-user-interaction characteristics.

Likely exposure

Exposure is most relevant for organizations running RethinkDB versions through 2.4.4, especially where database services or JSON-processing paths are reachable over a network. The source bundle does not confirm affected deployment configurations beyond the product and version range.

Exploitation context

The CVE is not listed as KEV in the provided data, and no cited source states active exploitation. Risk remains high because the CVSS vector indicates unauthenticated network reachability and high confidentiality, integrity, and availability impact.

Researcher notes

Public details are limited. The CVE record names cJSON.Cc and src/cjson modules but does not describe a trigger condition. The affected data includes “through v2.4.4,” while the structured affected version entry appears incomplete, so verify against upstream commits and releases.

Mitigation direction

  • Identify all RethinkDB instances and their versions.
  • Prioritize upgrades or vendor guidance for versions through 2.4.4.
  • Review GitHub PR 7163 as the referenced patch source.
  • Restrict network access to RethinkDB services where possible.
  • Monitor RethinkDB project channels for release or advisory updates.

Validation and detection

  • Confirm whether deployed RethinkDB versions are through 2.4.4.
  • Check whether the PR 7163 patch is present in deployed builds.
  • Verify RethinkDB is not exposed to untrusted networks.
  • Review logs for unusual crashes or JSON-processing anomalies.
  • Track CVE and upstream repository updates for corrected version details.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-120: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24810 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
10 (4.0)
Known Exploited
No
Published

Vector: 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/S:N/AU:Y/R:U/V:C/RE:M/U:Red

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
10CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/S:N/AU:Y/R:U/V:C/RE:M/U:Red——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

10Critical
CVSS 4.0 vector shape for CVE-2026-24810Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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/S:N/AU:Y/R:U/V:C/RE:M/U:Red

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
rethinkdbrethinkdb0affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.