CVE Intelligence
CISA KEV Critical Injection

CVE-2025-67038 — Lantronix EDS5000 Code Injection Vulnerability

An issue was discovered in Lantronix EDS5000 2.1.0.0R3. The HTTP RPC module executes a shell command to write logs when user's authentication fails. The username is directly concatenated with the command without any sanitization. This allow attackers to inject arbitrary OS commands into the username parameter. Injected commands are executed with root privileges.

Published Mar 11, 2026 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: icscert

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Public exploit/PoC (github)+6
  • EPSS 20% (30-day exploitation probability)+15
  • Technical severity (critical)+10
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Jun 23, 2026
EPSS FIRST
19.96%
ahead of 97% of scored CVEs · Oct 15, 2026
Affects
Lantronix
E210 series and 37 more
CVSS base
9.8
Critical · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

CISA required action CISA

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

US federal deadline: Jun 26, 2026 — passed 112 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Lantronix E210 series, Lantronix E213f102s Firmware, Lantronix E214f002s Firmware…).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  5. EPSS ahead of 97% of scored CVEs: prioritize it in the patch queue.
  6. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Lantronix E210 series < 3.21.0.0R1 Vulnerable CVE Program (cve.org) e CISA ADP
Lantronix E213f102s Firmware < 3.21.0.0R1 Vulnerable NIST National Vulnerability Database
Lantronix E214f002s Firmware < 3.21.0.0R1 Vulnerable NIST National Vulnerability Database
Lantronix E214f00cs Firmware < 3.21.0.0R1 Vulnerable NIST National Vulnerability Database
Lantronix E214g000s Firmware < 3.21.0.0R1 Vulnerable NIST National Vulnerability Database
Lantronix E214g001s Firmware < 3.21.0.0R1 Vulnerable NIST National Vulnerability Database
Lantronix E218f004s Firmware < 3.21.0.0R1 Vulnerable NIST National Vulnerability Database
Lantronix E218g107s Firmware < 3.21.0.0R1 Vulnerable NIST National Vulnerability Database
Lantronix E220 series < 3.21.0.0R1 Vulnerable CVE Program (cve.org) e CISA ADP
Lantronix E228g002s Firmware < 3.21.0.0R1 Vulnerable NIST National Vulnerability Database
Lantronix E228g004s Firmware < 3.21.0.0R1 Vulnerable NIST National Vulnerability Database
Lantronix E228g00cb28 Firmware < 3.21.0.0R1 Vulnerable NIST National Vulnerability Database
Lantronix E228g00cs Firmware < 3.21.0.0R1 Vulnerable NIST National Vulnerability Database
Lantronix EDS5000 series ≤ 2.1.0.0R3 Vulnerable CVE Program (cve.org) e CISA ADP
Lantronix Eds5008 Firmware < 2.2.0.0r1 Vulnerable NIST National Vulnerability Database
Lantronix Eds5016 Firmware < 2.2.0.0r1 Vulnerable NIST National Vulnerability Database
Lantronix Eds5032 Firmware < 2.2.0.0r1 Vulnerable NIST National Vulnerability Database
Lantronix G520 series < 2.6.0.4R6 Vulnerable CVE Program (cve.org) e CISA ADP
Lantronix G526gp12s Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix G526gp17s Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix G526gp1as Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix G526gp1asg Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix G526gp1cs Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix G527gp22s Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix G527gp27s Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix G527gp2as Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix G527gp2asg Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix G528gp2fs Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix G528gp2fsg Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix G528gp2fsgc Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix X300 series < 2.6.0.4R6 Vulnerable CVE Program (cve.org) e CISA ADP
Lantronix X300f202s Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix X303f202s Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix X304g000s Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix X304g002s Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix X304g007s Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix X304g00as Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database
Lantronix X304g00cs Firmware < 2.6.0.4R6 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.3 CVSS 4.0 Critical — — ics-cert@hq.dhs.gov via NIST National Vulnerability Database
9.3 CVSS 4.0 Critical — — icscert via CVE Program (cve.org) e CISA ADP
9.8 CVSS 3.1 Critical 3.9 5.9 ics-cert@hq.dhs.gov via NIST National Vulnerability Database
9.8 CVSS 3.1 Critical — — GitHub, Inc. via GitHub Security Advisories
9.8 CVSS 3.1 Critical — — icscert via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: ics-cert@hq.dhs.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-78 · OS Command Injection

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Jun 23, 2026
Federal deadline
Jun 26, 2026
passed 112 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Proofs of concept on GitHub

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 12, 2026 → Oct 15, 2026 · 4 reading(s) · max 19.96%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
  • Hunt retroactively in logs from before Jun 23, 2026 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · lantronix/eds5000 series, lantronix/g520 series, lantronix/x300 series, lantronix/e210 series, lantronix/e220 series
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Affected products added · lantronix/eds5008 firmware, lantronix/eds5016 firmware, lantronix/eds5032 firmware, lantronix/g526gp12s firmware, lantro
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Added to CISA KEV catalog
    Jun 22, 2026 · CISA
  • CVE published
    Mar 11, 2026 · icscert

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

8 on the record

Elsewhere on this site

Lantronix
every CVE for this vendor
2026-06
what else CISA listed that month
Injection
same class
CWE-78
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2025-67035 Lantronix EDS5000 OS Command Injection Mar 11, 2026
  • High CVE-2025-67036 Lantronix EDS5000, G520, and X300 OS Command Injection Mar 11, 2026
  • High CVE-2025-67037 Lantronix EDS5000, G520, and X300 OS Command Injection Mar 11, 2026
  • High CVE-2025-67034 Lantronix EDS5000, G520, and X300 OS Command Injection Mar 11, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-67038 is "Lantronix EDS5000 Code Injection Vulnerability", rated Critical. It affects E210 series (Lantronix); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.8 describes technical severity. EPSS 19.96% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.