CVE Intelligence
Medium Access control

CVE-2026-40713 — Improper Access Control in Dell Thinos

Dell 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.

Published Jun 2, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: dell

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+2
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.21%
ahead of 10% of scored CVEs · Oct 14, 2026
Affects
Dell
Thinos and 1 more
CVSS base
6.1
Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Dell Thinos, Dell ThinOS 10).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Dell Thinos < 2602_10.0765 Vulnerable NIST National Vulnerability Database
Dell ThinOS 10 < 2602_10.0765_T10 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Physical
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.1 CVSS 3.1 Medium 0.9 5.2 security_alert@emc.com via NIST National Vulnerability Database
6.1 CVSS 3.1 Medium — — dell via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N (score shown at the top: security_alert@emc.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-284 · Improper Access Control

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.21%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Audit administrative actions and access to resources outside each user’s normal pattern.
endpoint telemetry (EDR)authentication logsapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · dell/thinos 10
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 6.1
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Jun 2, 2026 · dell

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

Elsewhere on this site

Dell
every CVE for this vendor
Access control
same class
CWE-284
other pages naming this weakness

Related CVEs (same products)

  • Critical CVE-2026-81467 OS Command Injection in Dell Thinos Sep 10, 2026
  • High CVE-2026-81468 OS Command Injection in Dell Thinos Sep 10, 2026
  • Critical CVE-2026-81046 Improper Access Control in Dell Thinos Sep 10, 2026
  • High CVE-2026-81048 Command Injection in Dell Thinos Sep 10, 2026
  • Medium CVE-2026-81049 Dell ThinOS 10, versions prior to 2605_10.2616, contain a Missing Support for Integrity… Sep 10, 2026
  • Medium CVE-2026-81051 Dell ThinOS 10, versions prior to 2605_10.2616, contain a Security Version Number… Sep 10, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-40713 is "Improper Access Control in Dell Thinos", rated Medium. It affects Thinos (Dell); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.1 describes technical severity. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.