dbcve.org
Lms1000 FirmwareOperating system · Sick

CVE-2026-1627

HIGH · 8.1 CVSS v3.1 Published 2026-02-27
Fix available
A fix is available. Upgrade to 2.4.1 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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

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 · high confidence

The vulnerability stems from the SSH service supporting outdated and weak Message Authentication Code (MAC) algorithms, which could allow a man-in-the-middle attacker with network traffic interaction capabilities to manipulate transmitted data by exploiting these weak cryptographic primitives.

MitigationDisable weak MAC algorithms (such as md5, sha1, and their variants) in the SSH service configuration and restrict to strong MAC algorithms like hmac-sha2-256 and hmac-sha2-512, then restart the SSH service and verify connectivity.

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
Lms1000 FirmwareOperating system
Affected:< 2.4.1
Mrs1000 FirmwareOperating system
Affected:< 2.4.1

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. Determine the firmware version of the device
    Access the device management interface or check the system information page to identify the installed firmware version. Look for a version or build number field.
    Affected if The firmware version is below 2.4.1 (for LMS1000 or MRS1000 models)
  2. Verify SSH service is enabled
    Check if the SSH service is running on the device. This may be done through the device web interface, CLI access, or checking running services.
    Affected if SSH service is active and accessible on the network
  3. Locate SSH service configuration
    Find the SSH daemon configuration file. On many Linux-based devices this is typically /etc/ssh/sshd_config or accessible through the device management interface under SSH settings.
    Affected if SSH configuration file exists and is readable
  4. Inspect MAC algorithms configuration
    Examine the MACs configuration directive in the SSH config file. Look for any entries containing md5, sha1, or deprecated hash algorithms in the MACs line.
    Affected if Weak MAC algorithms such as hmac-md5, hmac-sha1, or their variants are listed in the MACs configuration

The device is affected if it runs firmware version below 2.4.1 on a Sick LMS1000 or MRS1000, has SSH enabled, and the SSH configuration includes weak MAC algorithms (md5, sha1, or variants).

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 2.4.1 or later
Fixed in 2.4.1
Interim mitigation

Disable weak MAC algorithms (such as md5, sha1, and their variants) in the SSH service configuration and restrict to strong MAC algorithms like hmac-sha2-256 and hmac-sha2-512, then restart the SSH service and verify connectivity.

Recommended fix High confidence

Firmware 2.4.1

  1. Identify the affected device model (LMS1000 or MRS1000) in your environment
  2. Check the current firmware version of the device
  3. Navigate to SICK's official support website and download firmware version 2.4.1 or later for your specific device model
  4. Follow SICK's documented firmware update procedure for the LMS1000 or MRS1000 device
  5. After completing the firmware upgrade, verify the SSH service no longer uses weak MAC algorithms by reviewing the SSH configuration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Lms1000 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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