Skip to content
IoT

CVE-2025-67034

8.8
High
EPSS 0.50%Mar 13, 2026

Authenticated command injection in EDS5000 management interface enabling root commands.

common questions

Is CVE-2025-67034 being exploited?

Not confirmed. CVE-2025-67034 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.50% probability of exploitation in the next 30 days.

How severe is CVE-2025-67034?

CVE-2025-67034 is rated High with a CVSS score of 8.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-67034?

Not known from our data. No patch reference has been recorded for CVE-2025-67034, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2025-67034 affect?

CVE-2025-67034 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-67034?

Patch when available; restrict management access; rotate credentials.

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

Root command execution via name param; attacker with auth can gain full control.

action required

Patch when possible

affected versions
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