Tracer SC: Memory Allocation with Excessive Size Value
CVE-2026-28253 is a high-severity memory allocation with excessive size value vulnerability in Tracer SC from Trane, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions v4.4 SP7, v6.3.2310 as the first without the flaw, so updating Tracer SC to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.35% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Tracer SC to v4.4 SP7 or v6.3.2310, whichever matches your release line, or a later version.
- Update Tracer Concierge to v6.3.2310 or a later version.
- Update Tracer Sc Firmware to 6.3.2310 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Trane | Tracer SC | before v4.4 SP7; before v6.3.2310 | v4.4 SP7, v6.3.2310 |
| Trane | Tracer Concierge | before v6.3.2310 | v6.3.2310 |
| Trane | Tracer Sc Firmware | 4.4 and earlier; 4.4; before 6.3.2310 | 6.3.2310 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.7 | High | CNA (hq.dhs.gov) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
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
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Memory Allocation with Excessive Size Value
The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.
How developers prevent this class of flaw
- Perform adequate input validation against any value that influences the amount of memory that is allocated. Define an appropriate strategy for handling requests that exceed the limit, and consider supporting a configuration option so that the administrator can extend the amount of memory to be used if necessary.
- Run your program using system-provided resource limits for memory. This might still cause the program to crash or exit, but the impact to the rest of the system will be minimized.
More Memory Allocation with Excessive Size Value vulnerabilities (CWE-789)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- cisa.gov/news-events/ics-advisories/icsa-26-071-01Third Party Advisory, US Government Resource
Other vulnerabilities in Tracer SC
- 9.8 Critical severity
- 9.8 Critical severity
- 7.5 High severity
- 9.8 Critical severity
Recent Memory Allocation with Excessive Size Value vulnerabilities
- 7.7 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.