Refused IP settings are stored in P-Net DCP Set requests
Key facts
- Attack vector
- Adjacent network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- —
- Confidentiality · integrity · availability
- None · Low · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA.
Summary
P-Net before 1.0.4 from RT-Labs stores the IP suite of a refused DCP Set request in both the current and non-volatile configuration. The device checks its state only after it has started saving the request, so a refused change is still kept (CWE-696). A host with adjacent network access can exploit this while an Application Relationship is active. After a restart, the device uses the refused address, which may stop it from answering the controller.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
Description from the CNA
P-Net before 1.0.4 copies the IP suite of a DCP Set request to the current and the non-volatile configuration, and starts saving it, before the state of the device is checked. If the request is refused, for example because an Application Relationship is active, the configuration is not restored and is still saved. After a restart the device uses the refused address, and may not answer the controller or may use its address. A host with ADJACENT network access can use this while an Application Relationship is active.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Update RT-Labs P-Net to version 1.0.4 or later, which fixes the flaw. Fixed version: 1.0.4.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
- Fix · CNA P-Net (RT-Labs) Fixed in 1.0.4
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
RT-Labs P-Net 1.0.4
9 records Highest priority Priority LOW 9 LOW
Other records, highest priority first
- TI-2026-91525 RPC session pool exhausted by unfinished fragmented requestsPriority LOW 31
- TI-2026-91523 Out-of-bounds write in RT-Labs P-Net via too many MCR blocksPriority LOW 31
- TI-2026-91518 P-Net accepts RTA alarm frames without checking their sourcePriority LOW 30
Timeline
- 2026-11-13 Threatist record created from CVE-2026-124761
- 2026-11-13 Alias added: GHSA-mpjp-g8wp-4mfr
- 2026-11-16 CISA SSVC decision points changed
References
More RT-Labs vulnerabilities
- TI-2026-82626 Out-of-bounds write when parsing AR Vendor Block requests in RT-Labs P-Net CVSS 4.0CRITICAL 9.3
- TI-2026-82632 Resource exhaustion from RPC sessions kept for unknown interface requests CVSS 4.0HIGH 8.7
- TI-2026-82630 NULL pointer dereference in RT-Labs P-Net on implicit read requests CVSS 4.0HIGH 8.7
- TI-2026-82627 NULL pointer dereference in P-Net lets remote attackers crash devices CVSS 4.0HIGH 8.7
- TI-2026-82625 Infinite loop in RT-Labs P-Net PDPortDataCheck record handling CVSS 4.0HIGH 8.7
- TI-2025-23482 Out-of-bounds write in RT-Labs P-Net CVSS 3.1CRITICAL 9.8
Sources
- CVE-2026-124761 · CVE Program
- CVE-2026-124761 · NVD
- FIRST EPSS
- GHSA-mpjp-g8wp-4mfr · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences