Cyber Resilience

CVE-2026-28253

Trane Tracer Sc Firmware ≤ 4.4

Published
12 March 2026
Modified
27 March 2026
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/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:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0031 23th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2026-28253 is a high-severity Memory Allocation with Excessive Size Value (CWE-789) vulnerability in Trane Tracer Sc Firmware. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SC-6 (Resource Availability) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-28253 is a Memory Allocation with Excessive Size Value vulnerability, classified under CWE-789, affecting Trane Tracer SC, Tracer SC+, and Tracer Concierge. Published on 2026-03-12T18:16:23.370, it carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), indicating high severity primarily due to its impact on availability.

An unauthenticated attacker with network access can exploit this vulnerability due to its low attack complexity and lack of required privileges or user interaction. Successful exploitation would trigger excessive memory allocation, leading to a denial-of-service condition on the affected systems.

The CISA ICS Advisory ICSA-26-071-01, available at https://www.cisa.gov/news-events/ics-advisories/icsa-26-071-01, provides further details on mitigation strategies for this vulnerability.

EU & UK References

Vulnerability Data

A Memory Allocation with Excessive Size Value vulnerability in Trane Tracer SC, Tracer SC+, and Tracer Concierge could allow an unauthenticated attacker to cause a denial-of-service condition

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-28254Same product: Trane Tracer Concierge
CVE-2026-28255Same product: Trane Tracer Concierge
CVE-2026-28252Same product: Trane Tracer Concierge
CVE-2026-28256Same product: Trane Tracer Concierge
CVE-2026-55379Shared CWE-789
CVE-2026-53428Shared CWE-789
CVE-2026-33174Shared CWE-789
CVE-2026-65315Shared CWE-789
CVE-2026-35549Shared CWE-789
CVE-2026-40891Shared CWE-789

Affected Assets

trane
tracer sc firmware
4.4 · ≤ 4.4
trane
tracer sc\+ firmware
≤ 6.3.2310
trane
tracer concierge
≤ 6.3.2310

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Input validation directly rejects or bounds untrusted size values before any allocation occurs.

Resource quotas and priority allocation limit the system-wide impact of an oversized request.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent coding flaws that trust unvalidated size values for allocations.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect and block excessive allocation flaws before deployment.

prevents

Secure development lifecycle includes input validation and size checks that prevent unbounded allocations.

prevents

Application security requirements mandate bounds checking on size parameters to avoid excessive memory allocation.

prevents

Secure architecture principles require resource-limit enforcement that mitigates uncontrolled memory requests.

prevents

Secure coding standards directly prohibit allocating memory from untrusted size values without validation.

none

Capacity management monitors overall resource use but does not prevent individual allocation bugs.

References