LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24825: a memory leak in ydb-platform/ydb with use of yajl_tree_parse function from src/yail module, which will cause out-of-memory in server and cause crash.

Missing Release of Memory after Effective Lifetime vulnerability in ydb-platform ydb (contrib/libs/yajl modules). This vulnerability is associated with program files yail_tree.C. This issue affects ydb: through 24.4.4.2.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-24825 is a memory leak in YDB’s bundled YAJL-related code. A network-accessible condition can consume server memory and crash the service. The published severity is medium, but business impact depends on whether YDB supports critical workloads and whether exposed endpoints can be reached by untrusted users.

Executive priority

Treat as a near-term availability risk for environments where YDB is business-critical or reachable by untrusted users. Prioritize inventory and patch validation, but do not treat it as confirmed active exploitation based on the provided evidence.

Technical view

The issue is CWE-401, missing memory release after effective lifetime, associated with contrib/libs/yajl modules and yail_tree.C. The description points to yajl_tree_parse usage in the src/yail module. Affected YDB versions are described as through 24.4.4.2. CVSS v4.0 is 6.9 with network attack vector and low attack complexity.

Likely exposure

Organizations running ydb-platform YDB through 24.4.4.2 may be exposed, especially where YDB services accept network input from untrusted or broad internal sources. The source bundle contains inconsistent affected-version metadata, so confirm applicability against the CVE record and vendor patch notes.

Exploitation context

The CVE is not listed as CISA KEV in the provided data, and no cited source states active exploitation. The risk is denial of service from memory exhaustion and server crash, not data theft or code execution based on the supplied sources.

Researcher notes

Evidence points to a memory-leak denial-of-service in YAJL parsing code. The only remediation reference supplied is GitHub PR #17570. The affected metadata is not fully clean: the narrative says through 24.4.4.2, while the structured affected entry is ambiguous. Validate against upstream details before broad conclusions.

Mitigation direction

  • Review the vendor pull request and release notes for the fixed YDB version.
  • Upgrade YDB if your deployed version is confirmed affected.
  • Restrict network access to YDB services to trusted clients where feasible.
  • Monitor YDB memory growth and crash events until remediation is complete.

Validation and detection

  • Inventory all YDB deployments and record exact versions.
  • Check whether deployments are through version 24.4.4.2.
  • Compare deployed code or packages with the vendor patch reference.
  • Review logs and monitoring for unexplained memory growth or crashes.
  • Confirm remediation by verifying the patched YDB build is deployed.
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-401: 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-24825 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
Medium
CVSS
6.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L/S:N/AU:Y/R:U/V:D/RE:L/U:Amber

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
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L/S:N/AU:Y/R:U/V:D/RE:L/U:Amber——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2026-24825Attack 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:N/VI:N/VA:L/SC:N/SI:N/SA:L/S:N/AU:Y/R:U/V:D/RE:L/U:Amber

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
ydb-platformydb0unaffected
Weakness

CWE details

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

CWE-401 · source CWE mapping

Missing Release of Memory after Effective Lifetime

Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.