Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2026-22646 is a medium-severity Generation of Error Message Containing Sensitive Information (CWE-209) vulnerability in Sick Incoming Goods Suite. Its CVSS base score is 4.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Software (T1592.002); ranked at the 30th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-11 (Error Handling) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-22646 is an information disclosure vulnerability (CWE-209) in certain applications from SICK, where error messages expose internal system details such as file paths, database errors, or software versions that should remain hidden from end users. This leakage enables attackers to perform reconnaissance by mapping the application's internal structure and identifying potential paths to more severe vulnerabilities. The issue carries a CVSS v3.1 base score of 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) and was published on 2026-01-15.
Attackers with low-privilege access, such as authenticated users, can exploit this vulnerability remotely over the network with low complexity and no user interaction. By deliberately triggering error conditions in the application, they obtain sensitive reconnaissance data, which provides insights into the system's architecture but does not allow direct confidentiality, integrity, or availability impacts beyond low-level information exposure.
SICK's PSIRT advisory at https://sick.com/psirt and the associated CSAF provider document sca-2026-0002 (available as JSON at https://www.sick.com/.well-known/csaf/white/2026/sca-2026-0002.json and PDF at https://www.sick.com/.well-known/csaf/white/2026/sca-2026-0002.pdf) detail mitigation steps. Additional guidance on ICS recommended practices is available from CISA at https://www.cisa.gov/resources-tools/resources/ics-recommended-practices.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-2793
Vulnerability Data
Certain error messages returned by the application expose internal system details that should not be visible to end users, providing attackers with valuable reconnaissance information (like file paths, database errors, or software versions) that can be used to map the…
more
application's internal structure and discover other, more critical vulnerabilities.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V16.5.1
Mitigating Controls (NIST 800-53 r5) AI
si-11 directly requires error messages to avoid revealing exploitable information about the system or its data.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require sanitized error handling to prevent sensitive data disclosure.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards explicitly forbid exposing sensitive data in errors.
Security testing can detect error messages that leak sensitive information.
Logging policy can require suppression of sensitive data in error messages.
Secure SDLC mandates error-handling rules that avoid leaking sensitive information.
Application security requirements can specify safe error messaging.
Secure architecture principles include proper exception handling.