CVE-2026-26342: Tattile s.r.l Smart+ · Insufficient Session Expiration
Affects Tattile s.r.l Smart+Source CVE Database V5
Not known to be exploited · CVSS 8.7 High.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Tattile s.r.l.Smart+ | Affected
| Fixed in– |
| Tattile s.r.l.Tolling+ | Affected
| Fixed in– |
| Tattile s.r.l.Smart+ Speed | Affected
| Fixed in– |
| Tattile s.r.l.Smart+ Traffic Light | Affected
| Fixed in– |
| Tattile s.r.l.Axle Counter | Affected
| Fixed in– |
| Tattile s.r.l.Vega53 | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2026-26342, organizations should implement the following specific measures: 1) Immediately audit and revoke all existing X-User-Tokens to invalidate potentially compromised sessions. 2) Restrict network access to the management interfaces of affected devices using network segmentation, firewalls, and VPNs to limit exposure to trusted administrators only. 3) Monitor device logs and network traffic for unusual or repeated authentication token usage patterns that may indicate unauthorized access. 4) Enforce strict token lifecycle management by implementing or requesting firmware updates that introduce automatic token expiration and session timeout mechanisms. 5) Where possible, replace or upgrade devices to versions with fixed token expiration logic. 6) Employ multi-factor authentication (MFA) on management interfaces if supported to reduce risk from token compromise. 7) Educate administrators on secure token handling and the risks of token reuse or exposure in logs. 8) Coordinate with Tattile s.r.l. for firmware patches or official guidance and apply updates promptly once available.
Description
Tattile Smart+, Vega, and Basic device families firmware versions 1.181.5 and prior implement an authentication token (X-User-Token) with insufficient expiration. An attacker who obtains a valid token (for example via interception, log exposure, or token reuse on a shared system) can continue to authenticate to the management interface until the token is revoked, enabling unauthorized access to device functions and data.