Security readout for executives and security teams
Plain-English summary
SmartIT Desktop Manager contains embedded credentials that an unauthenticated remote attacker may recover from application source code. Those credentials could enable control of managed systems, data theft, configuration changes, or service disruption. The affected-version information is unclear, so organizations using this product should investigate promptly.
Executive priority
Treat as an immediate investigation and containment priority because compromise could affect confidentiality, integrity, and availability across centrally managed endpoints. Assign ownership now, identify deployments, reduce network exposure, and obtain authoritative remediation guidance. Escalate incident review if suspicious authentication is found.
Technical view
CVE-2026-85146 is a CWE-798 hard-coded credentials flaw affecting Lightstar SmartIT Desktop Manager. Published data states attackers can obtain SSH service-account and SmartIT Agent credentials without authentication. CVSS 3.1 rates it 9.8: network-accessible, low complexity, no privileges or user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most concerning where SmartIT components, SSH services, or managed agents are reachable from untrusted networks. The supplied record lists version “0” and a default status of unaffected, which does not clearly identify affected releases. Confirm scope directly with Lightstar or TWCERT guidance.
Exploitation context
The supplied sources do not report observed exploitation, and the CVE is not identified as being in KEV. That absence does not prove exploitation has not occurred. Credential recovery is described as remotely possible without authentication, making exposed deployments attractive targets.
Researcher notes
The published vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Public details establish credential exposure but do not explain the precise source-code access path, credential scope, affected builds, patch availability, or observed attacks. Avoid assuming every SmartIT release is vulnerable until the vendor clarifies applicability.
Mitigation direction
- Consult Lightstar or TWCERT guidance for affected releases and an approved remediation.
- Restrict SmartIT management interfaces, agents, and associated SSH services to trusted networks.
- Rotate exposed SSH service-account and SmartIT Agent credentials after applying vendor-approved remediation.
- Check whether embedded credentials were reused across systems, and rotate matching credentials.
- Monitor vendor guidance for patches, upgrades, or credential-replacement procedures.
Validation and detection
- Inventory all SmartIT Desktop Manager servers and agents, including versions and network locations.
- Compare installed versions with current Lightstar or TWCERT affected-version guidance.
- Verify management and SSH services are not reachable from untrusted networks.
- Review authentication logs for unusual SSH or agent access, especially from unfamiliar addresses.
- Confirm credential rotation succeeded and previous credentials no longer authenticate.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-85146 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9twcertCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——twcertVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.twcert.org.tw/tw/cp-132-11176-a4cc2-1.htmlCVE reference, twcert · third-party-advisory
- https://www.twcert.org.tw/en/cp-139-11177-13ca3-2.htmlCVE reference, twcert · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Hard-coded Credentials
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.