Security readout for executives and security teams
Plain-English summary
Lantronix EDS5000 version 2.1.0.0R3 has command injection flaws in SSH management pages. A remote attacker could cause the device to run arbitrary operating-system commands as root, creating full device compromise risk.
Executive priority
Treat this as urgent for any exposed EDS5000 deployment. Root-level command execution on industrial network equipment can undermine availability and trust in device configuration.
Technical view
The issue affects SSH Client and SSH Server pages. Missing input sanitization in delete actions for objects including server keys, users, and known hosts allows OS command injection. The CVSS 3.1 vector is network-based, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely where Lantronix EDS5000 devices running 2.1.0.0R3 are reachable over the network and the affected SSH management pages or delete actions are accessible.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The impact is still severe because successful exploitation runs commands with root privileges.
Researcher notes
Evidence identifies multiple OS injection issues tied to delete actions, but the bundle does not include patch version, exploit details, or complete product CPE data. Avoid assuming broader Lantronix impact without vendor confirmation.
Mitigation direction
- Identify any Lantronix EDS5000 devices running 2.1.0.0R3.
- Review CISA ICSA-26-069-02 and vendor guidance for fixed firmware or mitigations.
- Restrict access to affected device management interfaces to trusted administrative networks.
- Monitor device logs and configuration changes for unexpected command execution indicators.
Validation and detection
- Inventory EDS5000 firmware versions and confirm whether 2.1.0.0R3 is present.
- Confirm whether SSH Client and SSH Server management pages are network-reachable.
- Review recent delete actions for server keys, users, and known hosts.
- Check whether CISA or Lantronix has published updated remediation guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-67035 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-069-02CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.