Skip to main content
Menu
CVEs

CVE

SICK scan XD crash via integer overflow in module size validation

Affects SICK AG sick_scan_xd versions before 3.10.0. Fixed in 3.10.0.

CVE-2026-123123EUVD-2026-128832GHSA-P3X2-H6VX-P97VPublished Updated Summary written by a model

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 3.10.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.10.0.

Summary

An attacker that is able to send a crafted network packet to the affected component may trigger an integer overflow during module size validation. This may cause insufficient bounds checking and result in out-of-bounds memory reads, potentially leading to a denial of service condition due to process termination.

cve.now Index

28Pcve.now Index 28 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 33 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 3.10.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-123123 (CVE-2026-123123), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-123123 (entry last updated 2026-11-18):
Affected:
- SICK AG sick_scan_xd: fixed in 3.10.0
Fixed versions: 3.10.0.
Conditions (all must be true for the bug to be hit):
- Affected product is SICK AG sick_scan_xd, fixed by upgrading to version 3.10.0. (source: https://www.cve.org/CVERecord?id=CVE-2026-123123)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-123123 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123123 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.sick.com/.well-known/csaf/white/2026/sca-2026-0018.pdf
- https://www.sick.com/psirt
- https://www.sick.com/media/docs/9/19/719/special_information_sick_operating_guidelines_cybersecurity_by_sick_en_im0106719.pdf
- https://www.cisa.gov/resources-tools/resources/ics-recommended-practices
- https://www.first.org/cvss/calculator/3.1
- https://www.sick.com/.well-known/csaf/white/2026/sca-2026-0018.json
- https://www.cve.org/CVERecord?id=CVE-2026-123123
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-123123
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-123123"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • SICK AG sick_scan_xd

    fixed in 3.10.0

Evidence 8

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-123123

Is CVE-2026-123123 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The checked facts do not describe what the flaw does. They give only the affected product, the version range, a CVSS score of 7.5 (high), and the fixed version.Source: cve.org

Which versions are affected by CVE-2026-123123?

sick_scan_xd: before 3.10.0.Source: cve.now feed data

Am I affected, and how do I check?

The listed range covers sick_scan_xd versions from the start up to but not including 3.10.0. To check an installation, compare its sick_scan_xd version against that range.Source: cve.org

How do I fix CVE-2026-123123?

The vendor recommends upgrading sick_scan_xd to version 3.10.0.Source: cve.org

More CVEs