Skip to content
Web

CVE-2025-67038

9.8
Critical
KEV · Exploited in wildEPSS 19%Patch availableMar 13, 2026

Root command injection via unsanitized username in HTTP RPC on Lantronix EDS5000.

common questions

Is CVE-2025-67038 being exploited?

Yes. CVE-2025-67038 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2025-67038?

CVE-2025-67038 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-67038?

Yes. A fix has been recorded for CVE-2025-67038. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-67038 affect?

CVE-2025-67038 affects Lantronix EDS5000 2.1.0.0R3. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-67038?

Patch when available; restrict HTTP RPC access.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Lantronix EDS5000 2.1.0.0R3
impact

Remote OS command execution with root privileges via username parameter in HTTP RPC, enabling full device control.

action required

Immediate action required

affected versions
Lantronix E210 series
  • affected< 3.21.0.0R1
vendor says fixed in3.21.0.0R1
Lantronix E220 series
  • affected< 3.21.0.0R1
vendor says fixed in3.21.0.0R1
Lantronix EDS5000 series
  • affected<= 2.1.0.0R3
vendor says fixed in2.2.0.0R1
Lantronix G520 series
  • affected< 2.6.0.4R6
vendor says fixed in2.6.0.4R6
Lantronix X300 series
  • affected< 2.6.0.4R6
vendor says fixed in2.6.0.4R6

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free