Skip to content
IoT

CVE-2026-63587

8.8
High
EPSS 0.27%Patch availableAug 25, 2026

SMS auth bypass allows unauthenticated SMS command execution on IE-SR-2TX-WL-4G.

common questions

Is CVE-2026-63587 being exploited?

Not confirmed. CVE-2026-63587 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.27% probability of exploitation in the next 30 days.

How severe is CVE-2026-63587?

CVE-2026-63587 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-2026-63587?

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

What does CVE-2026-63587 affect?

CVE-2026-63587 affects IE-SR-2TX-WL-4G cellular router, Devices using SMS control with 'Enable Password Authorization'. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-63587?

Disable SMS management, whitelist allowed numbers, block unknown SMS, and apply vendor patch when released.

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

executive summary
technical analysis
affected
IE-SR-2TX-WL-4G cellular routerDevices using SMS control with 'Enable Password Authorization'
impact

Remote unauthenticated attacker can disable SMS password auth by sending 5 failed SMS attempts, then execute SMS commands to tamper config, leak data, or disrupt service.

action required

Immediate action required

affected versions
Weidmueller Interface IE-SR-2TX-WL-4G-EU
  • affected>= 1.67 and < 1.74
Weidmueller Interface IE-SR-2TX-WL-4G-US-V
  • affected>= 1.67 and < 1.74

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