LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24812: An improper pointer arithmetic in root-project/root at builtins/zlib/inftrees.c

Vulnerability in root-project root (builtins/zlib modules). This vulnerability is associated with program files inftrees.C. This issue affects root: through 6.36.00-rc1.

CriticalCVSS 9.3Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-24812 is a critical flaw in ROOT’s bundled zlib code. The published score indicates potential remote, unauthenticated impact without user interaction. Organizations using ROOT through 6.36.00-rc1 should prioritize assessment and vendor-guided updating, especially where ROOT-backed services are network reachable.

Executive priority

High priority for organizations using ROOT in network-accessible or production workflows. The severity is critical, but urgency should be driven by confirmed presence of affected ROOT builds and vendor patch availability.

Technical view

The issue is described as improper pointer arithmetic associated with builtins/zlib/inftrees.c or inftrees.C in root-project/root. It is mapped to CWE-125 and affects ROOT through 6.36.00-rc1. CVSS 4.0 is 9.3 with network attack vector, low complexity, no privileges, and no user interaction.

Likely exposure

Exposure is likely limited to environments running affected ROOT versions, especially builds using the bundled zlib module. The CVSS vector indicates network reachability is relevant, but the provided sources do not describe specific vulnerable application workflows.

Exploitation context

No provided source states active exploitation, and the CVE is not listed as KEV in the bundle. Public evidence supports high theoretical severity, not confirmed exploitation in the wild.

Researcher notes

The public bundle identifies the vulnerable area and a patch reference but does not provide detailed root cause analysis, exploitability notes, or affected configuration nuances. Avoid assuming exploit status beyond the CVSS and vendor-linked patch evidence.

Mitigation direction

  • Identify ROOT deployments and versions across servers, workstations, containers, and scientific pipelines.
  • Review ROOT PR 18527 and apply the vendor-supported patch or fixed release when available.
  • If patching is delayed, reduce network exposure of ROOT-dependent services.
  • Monitor ROOT’s advisory blog and CVE record for updated remediation guidance.

Validation and detection

  • Confirm whether installed ROOT versions are through 6.36.00-rc1.
  • Check whether the bundled zlib module is present in deployed builds.
  • Verify whether changes from ROOT PR 18527 are included.
  • Run dependency or vulnerability scanning for CVE-2026-24812.
  • Document systems where remediation is pending and compensating controls apply.
Prepared
Confidence
medium
Sources
4

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-125: 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-24812 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
9.3 (4.0)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2026-24812Attack 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:L/VI:H/VA:H/SC:L/SI:H/SA:H/S:N/AU:Y/R:U/V:D/RE:M/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
root-projectroot0affected
Weakness

CWE details

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

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.