EM-20261105-V0CF
VulnerabilityHigh severity
ESPectre Vulnerability (CVE-2026-102739)
CVE-2026-102739
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 05 16:09 UTCC41 Red Hat Security Data
- Page Born
- Nov 05 17:17 UTCsecond source joined
- Last Signal
- Nov 05 17:17 UTC21 hours before snapshot
- Sources
- 21 official · 1 research, news or crowd
- Open For
- 20 hoursso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The ID never changes, and earlier addresses keep working. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 05 17:17 UTCC6 NVD published
- Scored: reachedNov 05 17:17 UTCCVSS 7.8
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: reachedNov 05 16:09 UTCC41 published
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- CVE-2026-102739 (CVSS 7.8) (opens source in a new tab) ESPectre is a Wi-Fi motion sensing platform for ESP32. Prior to 3.0.0-rc1, Micro-ESPectre analysis tools, including tools/6_optimize_filter_params.py, tools/1_analyze_raw_data.py, and tools/10_train_ml_model.py, load… High severityDatabaseC6 NVD CVE API 2.0
- Red Hat: CVE-2026-102739 (important) (opens source in a new tab) espectre: ESPectre: Arbitrary code execution via insecure dataset deserialization High severityVendorC41 Red Hat Security Data