dbcve.org
Tracer Sc FirmwareOperating system · Trane

CVE-2026-28253

HIGH · 7.5 CVSS v3.1 Published 2026-03-12
Fix available
A fix is available. Upgrade to 6.3.2310 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This vulnerability in Trane building automation controllers involves improper memory allocation sizing where unauthenticated network input triggers excessive memory allocation requests, potentially causing the device to exhaust memory resources and become unresponsive.

MitigationIsolate affected Trane controllers on restricted network segments, implement firewall rules to limit external access to port 80/443 on these devices, and contact Trane for available firmware updates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tracer Sc FirmwareOperating system
Affected:<= 4.4= 4.4
Tracer Sc\+ FirmwareOperating system
Affected:< 6.3.2310
Tracer ConciergeApplication
Affected:< 6.3.2310

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Trane controller model
    Locate the device physically or via network discovery and check the model labeling or web interface for Tracer Sc, Tracer Sc+, or Tracer Concierge
    Affected if Model is any of Tracer Sc, Tracer Sc+, or Tracer Concierge
  2. Check Tracer Sc firmware version
    Access the device web interface or administrative console and navigate to the firmware/version information section
    Affected if Model is Tracer Sc and version is <= 4.4 or exactly 4.4
  3. Check Tracer Sc+ firmware version
    Access the device web interface or administrative console and navigate to the firmware/version information section
    Affected if Model is Tracer Sc+ and version is less than 6.3.2310
  4. Check Tracer Concierge firmware version
    Access the device web interface or administrative console and navigate to the firmware/version information section
    Affected if Model is Tracer Concierge and version is less than 6.3.2310
  5. Verify network exposure
    Review firewall rules and network access controls to determine if the device management ports (80/443) are accessible from untrusted networks
    Affected if Device is externally accessible or accessible from untrusted network segments

User is affected if they have a Tracer Sc (any 4.4 or lower), Tracer Sc+ (<6.3.2310), or Tracer Concierge (<6.3.2310) that is network-accessible to untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.3.2310 or later
Fixed in 6.3.2310
Interim mitigation

Isolate affected Trane controllers on restricted network segments, implement firewall rules to limit external access to port 80/443 on these devices, and contact Trane for available firmware updates.

Recommended fix Moderate confidence

Tracer SC: upgrade to version > 4.4 (contact vendor for exact fixed release); Tracer SC+ and Tracer Concierge: upgrade to 6.3.2310 or later

  1. Identify the specific Tracer device model (Tracer SC, Tracer SC+, or Tracer Concierge) in your environment
  2. Determine the current firmware version installed on the device
  3. For Tracer SC devices: Upgrade firmware to a version newer than 4.4 (contact Trane for specific fixed release)
  4. For Tracer SC+ and Tracer Concierge devices: Upgrade firmware to version 6.3.2310 or later
  5. Verify the upgrade was successful and the device is operational
  6. Review CISA advisory ICSA-26-105-01 for additional vendor guidance if available
Caveat Review Trane release notes for any configuration or compatibility changes between current and target firmware versions before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tracer Sc Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,260
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28253 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28253 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data