Security readout for executives and security teams
Plain-English summary
CVE-2025-67038 is a critical flaw in Lantronix EDS5000 firmware 2.1.0.0R3. A login failure path can let an attacker run operating system commands as root through the username field. CISA lists it in KEV, indicating known exploitation.
Executive priority
Treat as urgent for any environment with Lantronix EDS5000 devices. KEV status means defenders should assume real-world attacker interest. Prioritize discovery, exposure reduction, and vendor-guided remediation ahead of routine patch cycles.
Technical view
The HTTP RPC module logs failed authentication by building a shell command with the supplied username. Because the username is not sanitized, arbitrary OS commands can be injected and executed with root privileges. The CVSS 3.1 score is 9.8, network-accessible, low complexity, no privileges, no user interaction.
Likely exposure
Organizations using Lantronix EDS5000 devices running 2.1.0.0R3 are the stated exposure. Risk is highest where device management interfaces are reachable from untrusted networks. The source bundle does not provide complete CPE data or broader affected version ranges.
Exploitation context
Active exploitation is supported by CISA KEV inclusion. The flaw is unauthenticated and network-reachable according to the CVSS vector, making exposed management interfaces high-risk. No exploit details are needed to assess urgency.
Researcher notes
The bundle identifies Lantronix EDS5000 2.1.0.0R3, root command execution, and KEV status. It does not include official patch version details, workaround specifics, CPEs, or observed exploitation details beyond KEV listing.
Mitigation direction
- Identify Lantronix EDS5000 devices and firmware versions immediately.
- Review CISA ICS advisory and Lantronix guidance for official fixes or mitigations.
- Restrict HTTP/RPC management access to trusted administrative networks only.
- Remove management interfaces from internet exposure where present.
- Increase monitoring for failed login activity and unusual device behavior.
- If compromise is suspected, isolate the device and begin incident response.
Validation and detection
- Confirm whether any EDS5000 devices run firmware 2.1.0.0R3.
- Check whether device management interfaces are reachable from untrusted networks.
- Review authentication failure logs for abnormal username patterns.
- Verify whether compensating network controls limit access to management services.
- Track CISA KEV and the CISA ICS advisory for remediation updates.
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-67038 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
- Yes
- 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.
CISA KEV status
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.
- Added to KEVCISA-ADP
CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.
- ADP timelineCISA-ADP
CVE-2025-67038 added to CISA KEV
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-06-23T00:00:00.000Z: CVE-2025-67038 added to CISA KEV
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-069-02CVE reference, mitre
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-67038CVE reference, CISA-ADP · government-resource
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.