ExploitedIn CISA KEVFix available

CVE-2025-67038

Q: Is CVE-2025-67038 actively exploited?

Yes. CVE-2025-67038 is on the CISA Known Exploited Vulnerabilities (KEV) catalog, meaning it has been confirmed as actively exploited in the wild. CISA requires federal agencies to patch by 2026-06-26.

Q: What is the CVSS score for CVE-2025-67038?

CVE-2025-67038 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Exploitation confirmed. First attested on 2026-06-23 by CISA-ADP, CISA KEV, GCVE · kevintel.

Published2026-03-11
Fixed in3.21.0.0R1
WeaknessCWE-78

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC

2026-03-1117:16CVE publishedNVD
2026-06-23Listed as exploited by GCVEGCVE
2026-06-23Exploitation first reportedCISA KEV
2026-06-23Added to the CISA KEV catalogCISA KEV
2026-06-2403:55SSVC exploitation set to activeCISA-ADP
2026-10-2319:23First public proof of conceptPoC-in-GitHub
2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2025-67038?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2025-67038?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Lantronix e213f102s firmwareversion to verify

Branch	Affected	Fixed in	Source
3.21	< 3.21.0.0R1	3.21.0.0R1	NVD

Lantronix e214f002s firmwareversion to verify

Branch	Affected	Fixed in	Source
3.21	< 3.21.0.0R1	3.21.0.0R1	NVD

Lantronix e214f00cs firmwareversion to verify

Branch	Affected	Fixed in	Source
3.21	< 3.21.0.0R1	3.21.0.0R1	NVD

30 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

ICSA-26-069-02 CISA5 known affected
Lantronix EDS3000PS and EDS5000 (Update B)
Lantronix EDS5000 series: <=2.1.0.0R3 · Lantronix G520 series: <2.6.0.4R6 · Lantronix X300 series: <2.6.0.4R6 · +2 more

Full record on NVD

Fix

Update Lantronix e213f102s firmware to 3.21.0.0R1
CISA’s required action: 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.due 2026-06-26
Vendor fix CISA ICSA-26-069-02 · 1 productEDS5000 series: Upgrade to version 2.2.0.0R1 or later. The patch can be found here: https://ltrxdev.atlassian.net/wiki/spaces/LTRXTS/pages/2538438657/Latest+Firmware+for+the+EDS5000+series+EDS5008+EDS5016+EDS5032. (CVE-2025-67034, CVE-2025-67035, CVE-2025-67036, CVE-2025-67037, CVE-2025-67038)
Vendor fix CISA ICSA-26-069-02 · 1 productG520 series: Upgrade to version 2.6.0.4R6 or later. The patch can be found here: https://ltrxdev.atlassian.net/wiki/spaces/LTRXTS/pages/1889828865/Latest+firmware+for+the+G520+Series+G526+G526RP+G527+G528. (CVE-2025-67034, CVE-2025-67036, CVE-2025-67037, CVE-2025-67038)
Vendor fix CISA ICSA-26-069-02 · 1 productX300 series: Upgrade to version 2.6.0.4R6 or later. The patch can be found here: https://ltrxdev.atlassian.net/wiki/spaces/LTRXTS/pages/2135261185/Latest+firmware+for+the+X300+Series+X300+X303+X304. (CVE-2025-67034, CVE-2025-67036, CVE-2025-67037, CVE-2025-67038)
Vendor fix CISA ICSA-26-069-02 · 1 productE210 series: Upgrade to version 3.21.0.0R1 or later. The patch can be found here: https://ltrxdev.atlassian.net/wiki/spaces/LTRXTS/pages/1914404865/Latest+firmware+ePack+for+the+E210+Series+E213+E214+E215+E218+Cellular+Routers. (CVE-2025-67038)
Vendor fix CISA ICSA-26-069-02 · 1 productE220 series: Upgrade to version 3.21.0.0R1 or later. The patch can be found here: https://ltrxdev.atlassian.net/wiki/spaces/LTRXTS/pages/1914437633/Latest+firmware+ePack+for+the+E220+Series+E224+E225+E228+Cellular+Routers. (CVE-2025-67038)
Mitigation from the vendor CISA ICSA-26-069-02 · 5 productsLantronix has released the following updates addressing these vulnerabilities. For more information, see the Lantronix Vulnerability Library (https://www.lantronix.com/technical-support/security-updates/vulnerability-disclosure-policy/vulnerability-library/?_gl=16c8bez_upMQ.._gaMzQwNjk5ODI5LjE3ODI5…

Advisories and patches

www.lantronix.comVendor Advisory

Detection

read 2026-10-23 19:24 UTC

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: 1 repository, unverifiedHORKimhab/CVE-2025-67038

CISA Known Exploited Vulnerability

Date Added: 2026-06-23
Patch Due Date: 2026-06-26
Ransomware Use: Unknown
Required Action: 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.

Sources

NVDCVE recordread 2026-10-23
CISA KEVKEV entry2026-06-23
GCVEexploitation2026-06-23
CISA-ADPSSVC decisionactive2026-06-24
OpenCVESSVC decisionactive—
CNACVSS 4.09.3read 2026-10-23
CNACVSS 3.19.8read 2026-10-23
CNAweakness (CWE)CWE-78read 2026-10-23
FIRST EPSSEPSS score20.0 %read 2026-10-23
PoC-in-GitHubproof of concept1read 2026-10-23

Technical details

CVSS v3 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 4.0 vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Published: 2026-03-11
Last Modified: 2026-09-08
NVD status: Analyzed

Frequently asked questions

What is CVE-2025-67038?

Is CVE-2025-67038 actively exploited?

Yes. CVE-2025-67038 is on the CISA Known Exploited Vulnerabilities (KEV) catalog, meaning it has been confirmed as actively exploited in the wild. CISA requires federal agencies to patch by 2026-06-26.

What is the CVSS score for CVE-2025-67038?

CVE-2025-67038 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, June 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database