LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1626: An attacker may exploit the use of weak CBC-based cipher suites in the device’s SSH service to potentially...

An attacker may exploit the use of weak CBC-based cipher suites in the device’s SSH service to potentially observe or manipulate parts of the encrypted SSH communication, if they are able to intercept or interact with the network traffic.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1626 concerns weak CBC-based SSH cipher suites on SICK LMS1000 and MRS1000 devices. If an attacker can intercept or interact with SSH network traffic, they may observe or manipulate parts of encrypted communication. The issue is rated medium by the source data and is not listed as CISA KEV.

Executive priority

Treat as a near-term industrial network hardening item, not an emergency based on current evidence. Prioritize sites where affected SICK devices are remotely managed, connected to shared networks, or reachable from less trusted zones.

Technical view

The vulnerability is CWE-327: use of a broken or risky cryptographic algorithm. The CVSS v3.1 score is 6.5 with network attack vector, low complexity, no privileges, and user interaction required. The reported impact emphasizes confidentiality, with no integrity or availability impact in the supplied vector, despite the narrative mentioning possible manipulation.

Likely exposure

Exposure is most relevant where SSH to SICK LMS1000 or MRS1000 devices is reachable over untrusted, shared, or poorly segmented networks. Organizations should verify actual installed firmware/product status against SICK advisory SCA-2026-0005 because the provided affected-version data is minimal.

Exploitation context

No active exploitation is supported by the supplied sources, and the CVE is not in CISA KEV. Practical risk depends on an attacker’s ability to intercept or interact with SSH traffic, which is more plausible on exposed, flat, or compromised industrial networks.

Researcher notes

The supplied record names SICK LMS1000 and MRS1000 but lists sparse affected-version information. Do not assume broader product impact. The CVSS vector and narrative differ slightly on integrity impact, so researchers should rely on vendor advisory details before drawing conclusions.

Mitigation direction

  • Review SICK advisory SCA-2026-0005 for vendor-approved remediation or configuration guidance.
  • Restrict SSH access to trusted administration networks and users only.
  • Apply ICS network segmentation and remote access controls consistent with CISA recommended practices.
  • Monitor SICK PSIRT for updates, patches, or revised affected-version information.

Validation and detection

  • Inventory SICK LMS1000 and MRS1000 devices and confirm SSH exposure paths.
  • Compare device details against SICK advisory SCA-2026-0005 and PSIRT updates.
  • Assess whether SSH management traffic crosses untrusted or shared network segments.
  • Review configurations for use of CBC-based SSH cipher suites where safely verifiable.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-327: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
cve · low confidence lookup

CVE-2026-1626 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2026-1626Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SICK AGSICK LMS10000unaffected
SICK AGSICK MRS10000unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-327 · source CWE mapping

Use of a Broken or Risky Cryptographic Algorithm

Use of a Broken or Risky Cryptographic Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.