CVE-2026-127124: RPC session pool exhausted by unfinished fragmented requests

Published Nov 13, 2026
·
Updated

P-Net before 1.0.4 keeps the RPC session that is allocated for a fragment of a request with an unknown activity UUID, without a timeout, when the rest of the request never arrives. A session that does not get an Application Relationship is also kept after the response. Repeated fragments or requests with different activity UUIDs exhaust the available sessions, one UDP packet per session. Once they are exhausted the device no longer answers a Connect request until it is restarted. An unauthenticated attacker with ADJACENT network access can use this to cause a denial of service.

Affected Software

1 affected component
RT-Labs P-Net<1.0.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade P-Net to a version that resolves this vulnerability.

    Fixed in 1.0.4

Event History

Nov 13, 2026
CVE Published
via MITRE·01:25 PM
Data Sourced
via MITRE·01:25 PM
RemedyDescriptionWeakness
Data Sourced
via NVD·02:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this denial of service?

P-Net versions before 1.0.4 are affected. Exploitation requires adjacent-network access because the attack is delivered using UDP packets to the target's RPC service.

2

Does exploitation require credentials or user interaction?

No. An unauthenticated attacker can trigger the condition, and no user interaction is required.

3

What happens when the attack succeeds?

Each unfinished fragmented request or request using a different activity UUID can retain an RPC session. After available sessions are exhausted, the device stops answering Connect requests until it is restarted.

4

Is there a workaround if the device cannot be updated immediately?

The provided information identifies adjacent-network access as a prerequisite. Restricting untrusted hosts from reaching the device's UDP RPC service can reduce exposure until an update is applied.

5

How can an operator recognize that the device may be under attack or affected?

A device that no longer responds to Connect requests and resumes doing so only after a restart may have exhausted its RPC session pool. The issue can be triggered with as little as one UDP packet per retained session.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203