CVE-2026-40713
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 · uneditedDell ThinOS 10, versions prior to ThinOS10 2602_10.0765, contain an Improper Access control vulnerability. An unauthenticated attacker with physical access could potentially exploit this vulnerability, leading to Information exposure.
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 · high confidenceDell ThinOS 10 versions prior to ThinOS10 2602_10.0765 contain an Improper Access Control vulnerability. An unauthenticated attacker with physical access to the thin client device can potentially exploit this vulnerability to gain unauthorized access to sensitive information.
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< 2602_10.0765CVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:P/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 ThinOS versionAccess the thin client system information orAbout screen, or use the system management interface to view the installed OS version. Common methods include checking the system properties in the ThinOS desktop environment or querying via the thin client management console.Affected if The displayed version number is below 2602_10.0765 (for example, 2602_10.0764 or earlier)
-
Confirm ThinOS 10 editionVerify that the installed system is Dell ThinOS 10 specifically, as this vulnerability affects only ThinOS 10 and not other ThinOS versions or Dell client systems.Affected if The system is running Dell ThinOS 10 with a version prior to 2602_10.0765
-
Check for physical access exposureAssess whether the thin client devices are located in areas where unauthorized individuals could gain physical access (public lobbies, unlocked offices, unattended desks).Affected if Devices are accessible to unauthorized persons and the ThinOS version is below 2602_10.0765
You are affected if your Dell ThinOS 10 installation shows a version number lower than 2602_10.0765 and the devices are accessible to unauthorized physical access.
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.
dbcve · scoped2602_10.0765
Upgrade Dell ThinOS 10 to version ThinOS10 2602_10.0765 or later to remediate the improper access control vulnerability.
ThinOS10 2602_10.0765
- Verify current ThinOS version by accessing the system locally or via management console
- Access Dell Wyse Management Suite or appropriate ThinOS management infrastructure
- Create a backup of current configuration if supported
- Deploy ThinOS version 2602_10.0765 or later to affected thin clients
- Verify successful deployment and test that the system functions normally
- Confirm the ThinOS version has been updated to 2602_10.0765 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40713 — 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-40713 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