basicsecurity.net
Proof, not just disclosure.
Threats / Lantronix / CVE-2025-67038
CVE-2025-67038 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-24

Lantronix EDS5000 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.

Verdict

Today item — known-exploited.

Confirmed exploited in the wild (CISA KEV). Prioritize remediation now and verify exposure.

CISA KEV Yes · 2026-06-233EPSS 0.00469 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
1 independent public report of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
cisa.gov ↗Confirmed
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-06-23).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.00469 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
FIRST EPSS ↗High
Severity / affected
Affected: Lantronix, EDS5000. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-78 OS Command Injection, CWE-94 Code Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-78 · OS Command InjectionCWE-94 · Code InjectionInjection
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board

Attacker/business narrative framing is pending triage for this record — see Coverage & confidence below. Facts and verdict above are derived deterministically from the public feed.

04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 1 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by mitre (CNA)

    • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Attacker/business narrative framing pending triage.
    • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.