CVE-2026-22908
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 · uneditedUploading unvalidated container images may allow remote attackers to gain full access to the system, potentially compromising its integrity and confidentiality.
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 · moderate confidenceThis vulnerability exists in the container image upload functionality where uploaded images are not validated before being processed. Attackers can upload malicious or crafted container images that, when deployed or extracted, allow remote code execution with full system access, compromising both integrity and confidentiality.
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< 1.4.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed firmware versionAccess the device web interface or check via CLI: cat /etc/version or look at the firmware info in the system settings. For Sick Tdc X401gl, navigate to Administration > System Info or use the command line interface to retrieve the firmware build version.Affected if Version is below 1.4.0 (e.g., 1.3.x, 1.2.x, etc.)
-
Locate container image upload configurationCheck the web interface under Settings > Container Registry or Container Management. Look for options related to image upload, import, or pull functionality. Examine configuration files in /etc/containerd/ or similar paths if CLI access is available.Affected if Container image upload feature is present and enabled in the configuration
-
Verify if container image upload has been usedReview system logs for entries containing 'image upload', 'crictl pull', 'docker load', or similar container-related operations. Check container registry audit logs if available.Affected if Container images have been uploaded or imported into the system
-
Check for untrusted or unsigned imagesExamine the container image storage directory (typically /var/lib/containerd/ or /var/lib/docker/) and list all stored images. Verify if any images lack cryptographic signatures or come from untrusted sources.Affected if Any container images are stored without signature verification or from untrusted registries
You are affected if the Sick Tdc X401gl firmware version is below 1.4.0 AND the container image upload feature is enabled or has been used with unvalidated images.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data1.4.0
Implement strict validation of all container images prior to upload, including image scanning for vulnerabilities, cryptographic signature verification, and content trust policies. Only allow images from trusted registries and require signed images.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22908 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22908 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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