# CVE-2026-26342: Tattile Smart+ / Vega / Basic <= 1.181.5 Insufficient Session Token Expiration

> Attackers with stolen tokens can bypass authentication on Tattile traffic devices due to insufficient session expiration, gaining unauthorized access to management functions.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Feb 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-w6wm-hqx9-7cq8

## What is CVE-2026-26342?

CVE-2026-26342 is a high-severity vulnerability in Tattile s.r.l. ANPR Mobile, published on 24 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2026-26342?

It affects 10 products.


Products: Tattile Anpr Mobile Firmware, Tattile Axle Counter Firmware, Tattile Basic Mk2 Firmware, Tattile Smart\+ Firmware, Tattile Smart\+ Speed Firmware, Tattile Smart\+ Traffic Light Firmware, Tattile Tolling\+ Firmware, Tattile Vega11 Firmware, Tattile Vega33 Firmware, Tattile Vega53 Firmware.

## How do I fix CVE-2026-26342?

No fix has been published for CVE-2026-26342 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-26342 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26342 exists.

## Other vulnerabilities in Tattile s.r.l. ANPR Mobile

- [CVE-2026-26341](https://insights.sbomify.com/CVE-2026-26341/): Tattile Smart+ / Vega / Basic <= 1.181.5 Default Credentials (critical 9.3)
- [CVE-2026-26340](https://insights.sbomify.com/CVE-2026-26340/): Tattile Smart+ / Vega / Basic <= 1.181.5 Unauthenticated RTSP Stream Disclosure (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26342 and fix it if it is affected.

What it is: CVE-2026-26342 is a high-severity vulnerability in Tattile s.r.l. ANPR Mobile, published on 24 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26342 exists.

Affected product: Tattile s.r.l. ANPR Mobile. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26342/ (Markdown: https://insights.sbomify.com/CVE-2026-26342/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26342
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26342
- OSV: https://osv.dev/vulnerability/CVE-2026-26342

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26342/
Summaries are generated and may contain mistakes; the official description above is the record.
