How severe is CVE-2025-61934?

CVE-2025-61934 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2025-61934 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (45th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-61934?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2025-61934 have an EU (EUVD) identifier?

Yes. CVE-2025-61934 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-35740.

When was CVE-2025-61934 published?

CVE-2025-61934 was published on 2025-10-23 and last updated on 2026-06-17.

CVE-2025-61934

CVE-2025-61934 is a critical-severity vulnerability with a CVSS 3.x base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-1327.

Key facts

Severity: Critical (CVSS 3.x base score 10.0)
CVSS v4: 9.3
EPSS exploit prediction: 1% (45th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-35740
Weakness: CWE-1327
Published: 2025-10-23
Last modified: 2026-06-17

Description

A binding to an unrestricted IP address vulnerability was discovered in Productivity Suite software version v4.4.1.19. The vulnerability allows an unauthenticated remote attacker to interact with the ProductivityService PLC simulator and read, write, or delete arbitrary files and folders on the target machine

Frequently asked questions

What is CVE-2025-61934?: A binding to an unrestricted IP address vulnerability was discovered in Productivity Suite software version v4.4.1.19. The vulnerability allows an unauthenticated remote attacker to interact with the ProductivityService PLC simulator and read, write, or delete arbitrary files and folders on the target machine
How severe is CVE-2025-61934?: CVE-2025-61934 has a CVSS 3.x base score of 10.0, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-61934 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (45th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-61934?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2025-61934 have an EU (EUVD) identifier?: Yes. CVE-2025-61934 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-35740.
When was CVE-2025-61934 published?: CVE-2025-61934 was published on 2025-10-23 and last updated on 2026-06-17.

References

Other CWE-1327 vulnerabilities

CVE-2023-1968 — Critical (CVSS 10.0): Instruments with Illumina Universal Copy Service v2.x are vulnerable due to binding to an unrestricted IP address. An…
CVE-2026-24015 — Critical (CVSS 9.8): A vulnerability in Apache IoTDB. This issue affects Apache IoTDB: from 1.0.0 before 1.3.7, from 2.0.0 before…
CVE-2026-0481 — Critical (CVSS 9.2): Unrestricted IP address binding in the AMD Device Metrics Exporter (ROCm ecosystem) could allow a remote attacker to…
CVE-2026-42503 — High (CVSS 8.8): gopls by default communicates via pipe. However, -port and -listen flags are supported as means of debugging. If…
CVE-2025-55322 — High (CVSS 7.3): Binding to an unrestricted ip address in GitHub allows an unauthorized attacker to execute code over a network.
CVE-2025-11538 — Medium (CVSS 6.8): A vulnerability exists in Keycloak's server distribution where enabling debug mode (--debug <port>) insecurely defaults…

Browse all CWE-1327 vulnerabilities →