Skip to main content
VulnerabilityPublished

CVE-2026-24790: Welker OdorEyes EcoSystem Pulse Bypass System with XL4 Controller · Missing Authentication

Affects Welker OdorEyes EcoSystem Pulse Bypass System with XL4 ControllerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
WelkerOdorEyes EcoSystem Pulse Bypass System with XL4 ControllerAffected
  • =All versions
Fixed in–

AI-suggested

Since no patches are currently available, organizations should implement strict network segmentation to isolate the OdorEyes EcoSystem Pulse Bypass System and its XL4 Controller from untrusted networks. Access to the device should be limited to authorized personnel only, using secure management networks with strong access controls such as VPNs and firewalls. Continuous monitoring for unusual network activity targeting the device is critical to detect potential exploitation attempts early. Employing intrusion detection/prevention systems (IDS/IPS) tuned for ICS protocols can help identify malicious commands. Where possible, implement compensating controls such as application-layer gateways or protocol whitelisting to restrict commands sent to the PLC. Regularly audit device configurations and network access logs. Additionally, conduct security awareness training for staff managing these systems to recognize and respond to potential threats.

Description

The underlying PLC of the device can be remotely influenced, without proper safeguards or authentication.

References

Community reviews

Loading reviews…