SICK Fixes Network Packet Handling in sick_scan_xd 3.10.0

P1 — VALIDATE AND UPDATEHigh · 7.5 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

Upgrade affected sick_scan_xd deployments to 3.10.0 and validate sensor communication and application recovery in a controlled maintenance window.

Confirm Scope And Apply The Supported Remediation

What to do now: Locate sick_scan_xd dependencies in ROS 2 applications, SDK consumers, containers and deployment images; record driver versions and network reachability. The advisory concerns the software driver and SDK, not a blanket vulnerability in every SICK LiDAR or RADAR device. Identify applications using versions before 3.10.0. Apply the vendor-recommended 3.10.0 release and rebuild dependent applications or images. Restrict network access to the affected component while scheduling the update. Verify the deployed driver version, normal sensor data flows and recovery behavior. Retain dependency inventories, network controls, rollout evidence and operational acceptance results.

Open the authoritative advisory

Last verified: 2026-11-18 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeSICK sick_scan_xd ROS 2 driver library and SDK
Advisorysca-2026-0018
CVECVE-2026-123123
Authoritative release date2026-11-18T14:47:00Z — initial publication in SICK’s CSAF tracking record.
Authority revision dateNo separate material revision is established for this release.
Affected versionssick_scan_xd versions before 3.10.0.
Fixed versionsick_scan_xd 3.10.0
CVSS base score7.5 (CVSS v3.1)
CVSS severityHigh
Exploitation statusThe cited authority does not confirm exploitation of these vulnerabilities in the wild.; no exploitation claim is inferred.

What Changed

SICK disclosed an integer overflow in network-packet size validation. A crafted packet can defeat bounds checking and trigger out-of-bounds reads, potentially terminating an application that uses the driver.

What To Validate Now

  1. Inventory. Locate sick_scan_xd dependencies in ROS 2 applications, SDK consumers, containers and deployment images; record driver versions and network reachability.
  2. Establish applicability. The advisory concerns the software driver and SDK, not a blanket vulnerability in every SICK LiDAR or RADAR device. Identify applications using versions before 3.10.0.
  3. Remediate. Apply the vendor-recommended 3.10.0 release and rebuild dependent applications or images. Restrict network access to the affected component while scheduling the update.
  4. Validate. Verify the deployed driver version, normal sensor data flows and recovery behavior. Retain dependency inventories, network controls, rollout evidence and operational acceptance results.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Coordinate testing with the responsible controls and safety owners. Do not send malformed test traffic to production equipment; the advisory’s availability impact does not establish code execution or compromise.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.