CVE-2026-22915
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 · uneditedAn attacker with low privileges may be able to read files from specific directories on the device, potentially exposing sensitive information.
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 is an authenticated file disclosure vulnerability allowing users with low privileges to read files from specific directories on the device. The vulnerability likely involves improper access control or path traversal in file read operations, potentially exposing sensitive configuration or system files.
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 dataall versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Sick TDC X401GL device in your environmentCheck your asset inventory or network scan results for devices with hostname, MAC OUI (Sick GmbH), or product identifier matching the TDC X401GL modelAffected if The device model matches Sick TDC X401GL and is network-accessible
-
Confirm firmware versionAccess the device web interface or use SNMP/sysinfo queries to retrieve the installed firmware version. Check device labeling or management console for firmware build informationAffected if Any firmware version is installed, as all versions are affected according to the advisory
-
Verify web management interface accessibilityAttempt to reach the device HTTP/HTTPS management port from your detection point. Check firewall rules and network segmentation for exposure to untrusted networksAffected if The web interface is accessible from network segments containing low-privilege or untrusted users
-
Review user account privilege levelsLog into the device administration panel and enumerate user accounts. Check for users assigned to roles below administrator or operator levelAffected if Low-privilege user accounts exist on the device
-
Inspect for anomalous file access patternsReview device logs, access logs, or SIEM records for file read operations targeting system directories (etc, config, var) originating from authenticated sessionsAffected if File read operations to sensitive directories are logged from non-administrator accounts
You are affected if a Sick TDC X401GL device with any firmware version is in your environment and low-privilege users can access the web management interface.
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 dataApply vendor patches when available and review user privilege assignments to ensure only necessary permissions are granted. If no patch exists, restrict network access to trusted users and monitor for unauthorized file access attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22915 — 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-22915 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