dbcve.org
Lms1000 FirmwareOperating system · Sick

CVE-2026-1626

CRITICAL · 9.1 CVSS v3.1 Published 2026-02-27
Fix available
A fix is available. Upgrade to 2.4.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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

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 SSH service on the device uses weak CBC (Cipher Block Chaining) mode cipher suites which are vulnerable to attacks such as CBC padding oracle attacks (e.g., Lucky Thirteen). An attacker positioned on the network path can intercept and potentially decrypt or manipulate encrypted SSH communication by exploiting the cryptographic weaknesses in these cipher modes.

MitigationDisable weak CBC-based cipher suites in the SSH daemon configuration and restrict the SSH service to use only strong CTR mode or GCM (AEAD) cipher suites, 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Identify the installed firmware version
    Access the device management interface or use the device's command-line interface to retrieve the firmware version. This is typically shown in the web UI under 'System Information' or via an SNMP/CLI command such as 'show version' or 'systeminfo'.
    Affected if The firmware version is lower than 2.4.1 (e.g., 2.3.x, 2.2.x, etc.)
  2. Confirm SSH service is enabled
    Check if the SSH daemon is running on the device. This can be done by looking for the SSH service in the device's web interface under 'Services' or by attempting to connect to TCP port 22.
    Affected if SSH service is active and accepting connections on the device
  3. Retrieve SSH daemon configuration
    Access the device's SSH daemon configuration file (commonly /etc/ssh/sshd_config or accessible via the device's web-based management under SSH settings). Look for lines containing 'Ciphers' or 'ciphers' keyword.
    Affected if The configuration file contains a 'Ciphers' directive listing cipher suites
  4. Identify cipher suite entries
    Examine the value of the Ciphers directive. Look for any CBC-mode cipher suites such as aes128-cbc, aes192-cbc, aes256-cbc, 3des-cbc, or blowfish-cbc.
    Affected if The cipher list includes any CBC-based cipher suites (e.g., aes128-cbc, aes256-cbc, 3des-cbc)
  5. Check for strong cipher alternatives
    Verify if the configuration contains only CTR mode (e.g., aes128-ctr, aes256-ctr) or GCM/AEAD ciphers (e.g., [email protected], [email protected]).
    Affected if No strong CTR or GCM ciphers are configured, or CBC ciphers are explicitly allowed

The device is affected if it runs firmware version below 2.4.1 AND has SSH enabled with CBC-based cipher suites configured.

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 CBC-based cipher suites in the SSH daemon configuration and restrict the SSH service to use only strong CTR mode or GCM (AEAD) cipher suites, then restart the SSH service and verify connectivity.

Recommended fix Moderate confidence

Lms1000 Firmware 2.4.1 and Mrs1000 Firmware 2.4.1

  1. 1. Obtain the firmware version 2.4.1 or later from the official SICK support website (sick.com) or your SICK representative
  2. 2. Review the firmware release notes for any specific upgrade instructions or prerequisites
  3. 3. Create a backup of the current device configuration if applicable
  4. 4. Upload the firmware file to the Lms1000 or Mrs1000 device using the SICK-provided firmware update tool or web interface
  5. 5. Verify the firmware update was successful by checking the device version information
  6. 6. After upgrade, confirm the SSH service is using strong cipher suites (CTR or GCM modes) rather than weak CBC-based ciphers
Caveat Industrial device firmware upgrades may affect existing configurations; review release notes and test in non-production environment before deploying

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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