dbcve.org
Tracer Sc FirmwareOperating system · Trane

CVE-2026-28252

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-12
Fix available
A fix is available. Upgrade to 6.3.2310 or later.
See remediation →
100/100
Remediation priority · Urgent
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 Use of a Broken or Risky Cryptographic Algorithm vulnerability in Trane Tracer SC, Tracer SC+, and Tracer Concierge could allow an attacker to bypass authentication and gain root-level access to the device.

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

The vulnerability involves use of a broken or risky cryptographic algorithm in Trane Tracer SC, Tracer SC+, and Tracer Concierge building management system controllers. This flaw allows attackers to bypass authentication mechanisms entirely and gain root-level administrative access to the device.

MitigationApply vendor-supplied firmware updates as they become available; restrict network access to the device and monitor for unauthorized access attempts.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 the Trane controller model
    Locate the device label or access the controller's web interface or administrative console to confirm whether the unit is a Tracer SC, Tracer SC+, or Tracer Concierge model.
    Affected if The device is any of these three models.
  2. Determine the installed firmware version
    Access the controller's administrative interface, typically via its web GUI or serial/SSH console, and locate the firmware version information in the system settings, about page, or device status section.
    Affected if A firmware version is displayed.
  3. Compare firmware to affected ranges for Tracer SC
    If the model is Tracer SC, check if the firmware version is 4.4 or lower (version <= 4.4).
    Affected if Firmware version is 4.4 or any version lower than 4.4.
  4. Compare firmware to affected ranges for Tracer SC+
    If the model is Tracer SC+, check if the firmware version is lower than 6.3.2310.
    Affected if Firmware version is less than 6.3.2310.
  5. Compare firmware to affected ranges for Tracer Concierge
    If the model is Tracer Concierge, check if the firmware version is lower than 6.3.2310.
    Affected if Firmware version is less than 6.3.2310.

The environment is affected if the device is a Trane Tracer SC (firmware <= 4.4), Tracer SC+ (firmware < 6.3.2310), or Tracer Concierge (firmware < 6.3.2310), because these versions contain the vulnerable cryptographic implementation that allows full authentication bypass.

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

Apply vendor-supplied firmware updates as they become available; restrict network access to the device and monitor for unauthorized access attempts.

Recommended fix Moderate confidence

Tracer SC+: firmware 6.3.2310 or later; Tracer Concierge: firmware 6.3.2310 or later; Tracer SC: contact Trane for fixed firmware

  1. 1. Identify the exact model and current firmware version of the Trane device (Tracer SC, Tracer SC+, or Tracer Concierge)
  2. 2. If running Tracer SC firmware <= 4.4, contact Trane technical support to obtain the appropriate fixed firmware version
  3. 3. If running Tracer SC+ or Tracer Concierge firmware < 6.3.2310, upgrade to firmware version 6.3.2310 or later
  4. 4. Follow Trane's official firmware update procedure, which typically involves using their tools (e.g., Trane Tracer SC Firmware Update Tool)
  5. 5. Verify the firmware upgrade was successful and the device is operational
  6. 6. After upgrade, confirm the cryptographic vulnerability is remediated by reviewing device security settings
  7. 7. Ensure the device is not directly accessible from untrusted networks; place behind a properly configured firewall
Caveat Review Trane release notes for Tracer SC+ and Concierge version 6.3.2310 for any functional changes; firmware upgrades on building automation devices may require recalibration or reconfiguration of connected systems

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

Fix this in Tracer Sc Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28252 — 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-28252 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