Quick answers
- Is CVE-2025-70082 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-70082 being exploited in the wild.
- How severe is CVE-2025-70082?
- Critical severity, with a CVSS score of 9.8, published 11 March 2026.
- Which products and versions are affected?
- Lantronix EDS3000PS firmware 3.1.0.0R2; Lantronix Eds3008ps1ns Firmware 3.1.0.0R2; Lantronix Eds3016ps1ns Firmware 3.1.0.0R2.
- Is there a fix for CVE-2025-70082?
- A patch was published on 2026-03-11: Lantronix released firmware 3.2.0.0R2 to address the issue Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-70082 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2025-70082?
- Check whether you run Lantronix EDS3000PS firmware, Lantronix Eds3008ps1ns, Lantronix Eds3008ps1ns Firmware or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability exists in the ltrx_evo component of Lantronix EDS3000PS firmware version 3.1.0.0R2. The flaw (CWE-620) allows the administrator password to be changed without knowledge of the current password. When chained with other vulnerabilities like authentication bypass (CWE-288) or OS command injection (CWE-78), a remote, unauthenticated attacker can achieve full root-level code execution and sensitive information disclosure. The attack is network-reachable and requires no user interaction. Lantronix has released firmware version 3.2.0.0R2 to address this issue.
Affected products
- Lantronix EDS3000PS firmware 3.1.0.0R2
- Lantronix EDS3008PS1NS 3.1.0.0R2
- Lantronix EDS3016PS1NS 3.1.0.0R2
Timeline
- 2026-03-10: advisory: CISA ICS Advisory ICSA-26-069-02 published
- 2026-03-11: disclosed: CVE published in NVD
- 2026-03-11: patched: Lantronix released firmware 3.2.0.0R2 to address the issue