LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1627: An attacker may exploit the use of outdated and weak MAC algorithms in the device’s SSH service to potentia...

An attacker may exploit the use of outdated and weak MAC algorithms in the device’s SSH service to potentially compromise the integrity of the SSH session, allowing manipulation of transmitted data if the attacker can 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-1627 concerns weak, outdated integrity checks in the SSH service on SICK LMS1000 and MRS1000 devices. If an attacker can interfere with network traffic, they may be able to manipulate data inside an SSH session. This is an integrity risk, not a reported data-theft or outage issue.

Executive priority

Treat as a medium-priority OT integrity issue. Prioritize devices reachable from broader corporate, remote-access, or untrusted networks. Business urgency increases if these sensors support safety, automation, or operational decision-making where manipulated management traffic could affect trust in device administration.

Technical view

The issue is CWE-327: use of broken or risky cryptographic algorithms. The CVSS 3.1 score is 6.5, vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N. The provided record names SICK LMS1000 and MRS1000 and describes weak SSH MAC algorithms that could allow session data manipulation.

Likely exposure

Exposure is most relevant where affected SICK devices have SSH reachable from networks an attacker could access or intercept. Internet exposure is not stated in the sources. OT environments with shared management networks, weak segmentation, or remote access paths should prioritize review.

Exploitation context

The sources do not state active exploitation, and the CVE is not listed as KEV. Exploitation requires the attacker to interact with network traffic, and the CVSS vector indicates user interaction is required. No exploit method is provided in the source bundle.

Researcher notes

The provided affected-version data is limited and appears ambiguous, including version value “0” and defaultStatus “unaffected.” No specific patch version is included in the bundle. Use the canonical SICK CSAF JSON/PDF for authoritative product status, remediation, and version details.

Mitigation direction

  • Review SICK advisory SCA-2026-0005 and PSIRT guidance for affected firmware and vendor remediation.
  • Apply vendor-provided updates or configuration changes when confirmed by SICK.
  • Restrict SSH access to trusted management networks only.
  • Use OT network segmentation and remote-access controls consistent with CISA ICS practices.
  • Disable or limit unnecessary management services where operationally feasible.

Validation and detection

  • Inventory SICK LMS1000 and MRS1000 devices and record firmware versions.
  • Confirm whether SSH is enabled and where it is reachable from.
  • Compare device versions against SICK advisory SCA-2026-0005.
  • Review SSH configuration for deprecated or weak MAC algorithms using approved administrative tools.
  • Validate firewall rules restrict device management access to trusted hosts.
Prepared
Confidence
medium
Sources
8

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-1627 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:N/I:H/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:N/I:H/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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.