BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-24825High confidence

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.

ydb-platform · ydb

6.9MediumCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 36 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.36% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs ydb-platform ydb and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 36 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-24825 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityydb: ydb: Denial of Service via memory leak
36 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • openshift-logging/cluster-logging-operator-bundle as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/cluster-logging-rhel9-operator as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/eventrouter-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/fluentd-rhel8 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/fluentd-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/log-file-metric-exporter-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/logging-view-plugin-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/vector-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • 3scale-amp2/backend-rhel7 as a component of Red Hat 3scale API Management Platform 2
  • 3scale-amp2/backend-rhel8 as a component of Red Hat 3scale API Management Platform 2
  • 3scale-amp2/zync-rhel7 as a component of Red Hat 3scale API Management Platform 2
  • 3scale-amp2/zync-rhel8 as a component of Red Hat 3scale API Management Platform 2
Summary
A flaw was found in ydb. This memory management vulnerability, identified as a 'Missing Release of Memory after Effective Lifetime', exists within the `contrib/libs/yajl` modules, specifically affecting the `yail_tree.C` program file. A remote attacker could exploit this by repeatedly triggering memory allocations without proper deallocation. This could lead to resource exhaustion, ultimately causing a Denial of Service (DoS) for the affected system.
Remediation
Fix deferred
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-4806

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 36 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Missing Release of Memory after Effective Lifetime → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-401 ↗

CWE-401: Missing Release of Memory after Effective Lifetime. The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
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

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VALowVulnerable-system availability: A successful attack can cause a limited loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SALowSubsequent-system availability: A successful attack can cause a limited loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-401
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20260128Security Bulletin 28 Jan 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 28 Jan 2026, published on 28 January 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 27 Jan 2026 · Last source change 27 Jan 2026, 16:57 UTC · CWE-401 · Missing Release of Memory after Effective Lifetime

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-4806
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    openshift-logging/cluster-logging-operator-bundle as a component of Logging Subsystem for Red Hat OpenShift; openshift-logging/cluster-logging-rhel9-operator as a component of Logging Subsystem for Red Hat OpenShift; openshift-logging/eventrouter-rhel9 as a component of Logging Subsystem for Red Hat OpenShift; openshift-logging/fluentd-rhel8 as a component of Logging Subsystem for Red Hat OpenShift; openshift-logging/fluentd-rhel9 as a component of Logging Subsystem for Red Hat OpenShift; openshift-logging/log-file-metric-exporter-rhel9 as a component of Logging Subsystem for Red Hat OpenShift; openshift-logging/logging-view-plugin-rhel9 as a component of Logging Subsystem for Red Hat OpenShift; openshift-logging/vector-rhel9 as a component of Logging Subsystem for Red Hat OpenShift; 3scale-amp2/backend-rhel7 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/backend-rhel8 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/zync-rhel7 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/zync-rhel8 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/zync-rhel9 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp20/backend as a component of Red Hat 3scale API Management Platform 2; 3scale-amp21/backend as a component of Red Hat 3scale API Management Platform 2; 3scale-amp21/zync as a component of Red Hat 3scale API Management Platform 2; 3scale-amp22/backend as a component of Red Hat 3scale API Management Platform 2; 3scale-amp22/zync as a component of Red Hat 3scale API Management Platform 2; 3scale-amp24/backend as a component of Red Hat 3scale API Management Platform 2; 3scale-amp24/zync as a component of Red Hat 3scale API Management Platform 2; 3scale-amp25/backend as a component of Red Hat 3scale API Management Platform 2; 3scale-amp25/zync as a component of Red Hat 3scale API Management Platform 2; 3scale-amp26/backend as a component of Red Hat 3scale API Management Platform 2; 3scale-amp26/zync as a component of Red Hat 3scale API Management Platform 2; yajl-devel as a component of Red Hat Enterprise Linux 6; yajl.src as a component of Red Hat Enterprise Linux 6; yajl-devel as a component of Red Hat Enterprise Linux 7; yajl.src as a component of Red Hat Enterprise Linux 7; yajl as a component of Red Hat Enterprise Linux 8; yajl-devel as a component of Red Hat Enterprise Linux 8; and 5 more
    After
    openshift-logging/cluster-logging-operator-bundle as a component of Logging Subsystem for Red Hat OpenShift; openshift-logging/cluster-logging-rhel9-operator as a component of Logging Subsystem for Red Hat OpenShift; openshift-logging/eventrouter-rhel9 as a component of Logging Subsystem for Red Hat OpenShift; openshift-logging/fluentd-rhel8 as a component of Logging Subsystem for Red Hat OpenShift; openshift-logging/fluentd-rhel9 as a component of Logging Subsystem for Red Hat OpenShift; openshift-logging/log-file-metric-exporter-rhel9 as a component of Logging Subsystem for Red Hat OpenShift; openshift-logging/logging-view-plugin-rhel9 as a component of Logging Subsystem for Red Hat OpenShift; openshift-logging/vector-rhel9 as a component of Logging Subsystem for Red Hat OpenShift; 3scale-amp2/backend-rhel7 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/backend-rhel8 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/zync-rhel7 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/zync-rhel8 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp2/zync-rhel9 as a component of Red Hat 3scale API Management Platform 2; 3scale-amp20/backend as a component of Red Hat 3scale API Management Platform 2; 3scale-amp21/backend as a component of Red Hat 3scale API Management Platform 2; 3scale-amp21/zync as a component of Red Hat 3scale API Management Platform 2; 3scale-amp22/backend as a component of Red Hat 3scale API Management Platform 2; 3scale-amp22/zync as a component of Red Hat 3scale API Management Platform 2; 3scale-amp24/backend as a component of Red Hat 3scale API Management Platform 2; 3scale-amp24/zync as a component of Red Hat 3scale API Management Platform 2; 3scale-amp25/backend as a component of Red Hat 3scale API Management Platform 2; 3scale-amp25/zync as a component of Red Hat 3scale API Management Platform 2; 3scale-amp26/backend as a component of Red Hat 3scale API Management Platform 2; 3scale-amp26/zync as a component of Red Hat 3scale API Management Platform 2; yajl-devel as a component of Red Hat Enterprise Linux 6; yajl.src as a component of Red Hat Enterprise Linux 6; yajl-devel as a component of Red Hat Enterprise Linux 7; yajl.src as a component of Red Hat Enterprise Linux 7; yajl as a component of Red Hat Enterprise Linux 8; yajl-devel as a component of Red Hat Enterprise Linux 8; and 6 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2026-4806↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-24825 · cve.blacktree.nl