dbcve.org
Tracer Sc FirmwareOperating system · Trane

CVE-2026-28254

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 Missing Authorization vulnerability in Trane Tracer SC, Tracer SC+, and Tracer Concierge could allow an unauthenticated attacker to access sensitive information through unprotected APIs.

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

Missing Authorization vulnerability in Trane Tracer SC, Tracer SC+, and Tracer Concierge building management systems allows unauthenticated attackers to access sensitive information through unprotected APIs. The vulnerability has a CVSS score of 7.5 (HIGH), indicating significant risk to confidentiality of building automation data.

MitigationImplement proper authentication and authorization checks on all API endpoints, restrict network access to management interfaces, and apply any vendor-provided patches for these Trane building management devices.

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
None
Availability
None

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

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 device model
    Access the device web interface, system information page, or check physical device labels to determine if the device is a Tracer SC, Tracer SC+, or Tracer Concierge building management controller
    Affected if The device model is Tracer SC, Tracer SC+, or Tracer Concierge
  2. Determine the installed firmware version
    Log into the device administrative interface and navigate to the system information, about, or firmware version page to find the currently installed firmware version number
    Affected if The firmware version is 4.4 or lower for Tracer SC, or less than 6.3.2310 for Tracer SC+ or Tracer Concierge
  3. Verify API endpoint authentication requirements
    Using a web browser or HTTP client, attempt to access common API endpoints on the device (such as /api/, /rest/, or /web/services/) without providing any authentication credentials
    Affected if The API endpoints return sensitive data or functional responses without requiring login or authentication tokens

You are affected if you have a Tracer SC (firmware <= 4.4), Tracer SC+ (< 6.3.2310), or Tracer Concierge (< 6.3.2310) device AND its API endpoints are accessible without authentication.

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

Implement proper authentication and authorization checks on all API endpoints, restrict network access to management interfaces, and apply any vendor-provided patches for these Trane building management devices.

Recommended fix Moderate confidence

Tracer SC: version > 4.4; Tracer SC+: version >= 6.3.2310; Tracer Concierge: version >= 6.3.2310

  1. Check the current firmware version on the Tracer SC, Tracer SC+, or Tracer Concierge device
  2. For Tracer SC devices: Upgrade firmware to a version newer than 4.4 (contact Trane for specific fixed version)
  3. For Tracer SC+ devices: Upgrade firmware to version 6.3.2310 or later
  4. For Tracer Concierge devices: Upgrade firmware to version 6.3.2310 or later
  5. After upgrade, verify that API endpoints now require proper authentication
  6. Consult Trane technical documentation or support for upgrade procedures specific to your device model
Caveat Review release notes for any configuration or compatibility changes in the new firmware version

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
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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