CVE-2026-28255
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 · uneditedA Use of Hard-coded Credentials vulnerability in Trane Tracer SC, Tracer SC+, and Tracer Concierge could allow an attacker to disclose sensitive information and take over accounts.
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 confidenceA Use of Hard-coded Credentials vulnerability exists in Trane Tracer SC, Tracer SC+, and Tracer Concierge building management systems. Attackers who discover these embedded credentials can gain unauthorized access, exfiltrate sensitive system information, and compromise user accounts. The hard-coded nature means these credentials are present in the firmware or software and may be discoverable through reverse engineering or leaked documentation.
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<= 4.4= 4.4< 6.3.2310< 6.3.2310CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Tracer device model and firmware versionAccess the device web interface, check the system information page, or use SNMP/serial console to retrieve the firmware version. For web interface, navigate to the About or System Info section. For command line, check the device's system settings or banner information.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)
-
Confirm the specific Tracer product lineVerify whether the device is a Tracer SC, Tracer SC+, or Tracer Concierge unit. This information is typically displayed on the main status page or device identification screen of the web interface.Affected if The device is any of the three affected product lines within the specified version ranges
-
Determine if network management interfaces are enabledCheck the device network configuration to see if HTTP/HTTPS web interfaces, BACnet, or other management protocols are accessible over the network. Review port listings and service statuses.Affected if The device has exposed network management interfaces that could accept the hard-coded credentials
-
Inspect for presence of default or hard-coded accountsReview any locally stored configuration backups, exported device configs, or firmware files for strings that may represent hard-coded credentials or default accounts. Use standard archive/config inspection tools on any backup files.Affected if Configuration files or firmware contain embedded credentials that differ from site-specific passwords
-
Audit network access to the deviceReview network segmentation, firewall rules, and access control lists to determine if the Tracer device management interfaces are reachable from untrusted networks or the internet.Affected if The device management interface is accessible from networks where unauthorized attackers could attempt to use discovered hard-coded credentials
You are affected if you are running Trane Tracer SC firmware <= 4.4, Tracer SC+ firmware < 6.3.2310, or Tracer Concierge < 6.3.2310 with network-accessible management interfaces.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.3.2310
Replace all hard-coded credentials with unique, strong passwords or implement proper credential management. Apply any vendor-supplied patches, network segment the affected systems, and audit for additional hard-coded secrets.
Tracer SC+: 6.3.2310 or later; Tracer Concierge: 6.3.2310 or later; Tracer SC: Contact vendor for version > 4.4
- 1. Identify the exact firmware version currently installed on the Tracer SC, Tracer SC+, or Tracer Concierge device
- 2. For Tracer SC devices: Contact Trane technical support to confirm if a firmware version greater than 4.4 is available and obtain the upgrade path
- 3. For Tracer SC+ and Tracer Concierge devices: Upgrade firmware to version 6.3.2310 or later
- 4. After upgrading, change all default credentials and ensure any hardcoded credentials used for integration are replaced with strong, unique credentials
- 5. Verify the upgrade was successful and confirm the hardcoded credentials are no longer present
- 6. Review access logs for any unauthorized access attempts that may have occurred prior to the remediation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28255 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28255 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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