CVE-2025-41656: Pilz IndustrialPI 4 with Firmware Bullseye · Missing Authentication
Affects Pilz IndustrialPI 4 with Firmware BullseyeSource CVE Database V5
Not known to be exploited · 12% EPSS · CVSS 10.0 Critical.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 12.3% chance of exploitation in 30 days – higher than 96% 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:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Pilz IndustrialPI 4 with Firmware Bullseye | Affected
| Fixed in– |
AI-suggested
1. Immediate network segmentation: Isolate Pilz IndustrialPI 4 devices from general IT networks and restrict access to trusted management networks only. 2. Implement strict firewall rules: Block all inbound traffic to the Node_RED server ports from untrusted sources. 3. Configure authentication manually: Since authentication is not enabled by default, administrators must enable and enforce strong authentication mechanisms on the Node_RED server as soon as possible. 4. Monitor network traffic: Deploy intrusion detection/prevention systems (IDS/IPS) to detect anomalous access attempts to the Node_RED server. 5. Apply compensating controls: Use VPNs or secure tunnels for remote access to these devices to prevent direct exposure. 6. Vendor engagement: Maintain close contact with Pilz for updates and patches; prioritize patch deployment once available. 7. Conduct regular security audits and penetration testing focused on OT environments to identify similar misconfigurations. 8. Develop and rehearse incident response plans specific to OT device compromise scenarios to minimize impact if exploitation occurs.
Description
An unauthenticated remote attacker can run arbitrary commands on the affected devices with high privileges because the authentication for the Node_RED server is not configured by default.