CVE-2025-67038: Lantronix EDS5000 Code Injection Vulnerability

P0 — ACT NOWCISA KEVRANSOMWARE: UNKNOWNFORENSIC TRIAGE: NO

Quick Answer

CISA describes CVE-2025-67038 as username-parameter command injection on Lantronix EDS5000, with commands running as root. Identify the exact EDS5008, EDS5016 or EDS5032 model, hardware revision and firmware before planning an update. The vendor download page does not establish which build fixes this CVE. Preserve device and off-device evidence; installing a newer image alone cannot prove the issue or earlier compromise is resolved.

Fix Or Immediate Action

What to do now: Confirm the exact product, release, exposure, and prerequisites against the live vendor advisory, then apply the vendor-listed update or mitigation. CISA added CVE-2025-67038 to KEV on 2026-06-23.

Open Lantronix EDS5000 firmware information

Evidence check: Vendor evidence and unresolved source limits are described below. CISA KEV catalog 2026.10.02 was checked on October 2. Preserve the distinction between vendor publication history, catalog dates and evidence from your deployment; no patch or exploit test is claimed.

Context

Scope And Impact In Plain Language

Who should check: Anyone who manages Lantronix EDS5000.

When this applies: Only when the exact product, version, and required configuration match the live vendor advisory. Owning the product family alone does not mean the device is vulnerable.

What could happen: A successful attacker may be able to run attacker-chosen commands or software on the affected system, subject to the access and configuration requirements in the advisory.

Not sure? Find the product name and version in the device or application, then compare them with the affected-products section of the linked vendor notice.

Status At A Glance

Product scopeLantronix — EDS5000
CVECVE-2025-67038
TechGeeks response tierP0 — confirm an exact match and act now
CISA KEV added2026-06-23
Vendor severityConsult the live vendor advisory; no vendor severity is inferred from KEV status.
CVSSConsult the live vendor advisory; no CVSS value is inferred from KEV status.
Ransomware fieldUnknown — this is not the same as No; CISA has not marked the field Known.
Forensic-triage fieldNo in the current CISA field; organizations should still investigate when exposure or evidence warrants it.
CWECWE-78, CWE-94
Federal remediation date2026-06-26 — applies to covered federal agencies; other organizations should set a risk-based deadline.

What Happened

Lantronix EDS5000 Code Injection Vulnerability. Lantronix EDS5000 contains a code injection vulnerability that could allow attackers to inject arbitrary OS commands into the username parameter. Injected commands are executed with root privileges. CISA's KEV listing confirms exploitation evidence, but it does not state how widespread the activity is or prove that any particular installation was compromised.

Affected Scope

Match the EDS5000 model and hardware revision to Lantronix's firmware notes. The October 1 release notes cover EDS5008, EDS5016 and EDS5032, and require at least 2.4.0.0R1 for hardware revision B11 or later. That hardware minimum is not a CVE-specific fix claim.

Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.

Steps

What To Do Now

  1. Confirm. Inventory every EDS5000 asset and record its exact version, patch level, role, relevant configuration, and exposure.
  2. Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
  3. Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open Lantronix EDS5000 firmware information.
  4. Remediate. Confirm the exact product, release, exposure, and prerequisites against the live vendor advisory, then apply the vendor-listed update or mitigation. CISA added CVE-2025-67038 to KEV on 2026-06-23.
  5. Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
  6. Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.

Fixed Releases And Mitigation

Permanent Fix

The 2.4.0.0R1 release notes do not identify CVE-2025-67038, so this notice cannot certify that build as its fix. Obtain the CVE-specific mapping from Lantronix. The notes also require clearing Keep Settings for the listed 2.1.0.x-or-earlier and 2.3.0.x upgrade paths, and prohibit Percepxion upgrades from 2.3.0.0R7/2.3.0.1R1 to this release; preserve configuration and recovery information before following those instructions.

Workaround Or Temporary Mitigation

Consult the live vendor advisory for the exact affected and fixed release matrix; no release number is asserted here.

Important boundary: A workaround, access restriction, or provider-side control may reduce risk while the update is prepared, but it does not necessarily remove vulnerable code or erase an earlier compromise. Install the vendor-approved update when one is available.

Investigation And Recovery

CISA's KEV record does not mark this entry for forensic triage. That field is not proof of a clean system; consult the vendor advisory for indicators and recovery guidance.

When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.

Notes

Exploitation Evidence

Vendor statement: Lantronix's firmware notes do not supply a CVE-specific exploitation assessment. CISA independently records exploitation and a June 23 KEV addition; do not treat the download page as confirming or denying campaign activity.

CISA statement: CVE-2025-67038 was added to KEV on 2026-06-23. The ransomware field is Unknown, and the forensic-triage field is No. These are separate signals.

Validation And Boundaries

This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.

Related TechGeeks Resources

References

Wrap-Up

Record whether CVE-2025-67038 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.

Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.