PatchSiren

PatchSiren cyber security CVE debrief

CVE-2025-41769 Phoenix Contact CVE debrief

The CVE-2025-41769 record details a critical buffer overflow vulnerability in the PROFINET service of an affected device. This vulnerability, with a CVSS score of 9.3, allows an unauthenticated remote attacker to potentially reboot the device or execute arbitrary code. The vulnerability exists in the default configuration of the device. Organizations, particularly those in industrial control systems, manufacturing, and critical infrastructure sectors, should be aware of this vulnerability. The NVD entry for this CVE is currently Deferred. To address this vulnerability, it is crucial to review device configurations and PROFINET service setups, implement compensating controls, verify vendor remediation, apply patches or updates, conduct inventory checks, and monitor for suspicious activity.

Vendor
Phoenix Contact
Product
AXC F 1152
CVSS
CRITICAL 9.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-12
Original CVE updated
2026-09-03
Advisory published
2026-08-12
Advisory updated
2026-09-03

Who should care

Organizations using devices with the affected PROFINET service should be aware of this critical vulnerability. Particularly, those in industrial control systems, manufacturing, and critical infrastructure sectors are advised to review their device configurations and PROFINET service setups. IT and security teams responsible for maintaining these systems should prioritize verifying vendor remediation, applying patches or updates, and monitoring for suspicious activity. Additionally, conducting inventory checks to identify potentially affected devices is crucial for risk management and mitigation efforts related to CVE-2025-41769.

Technical summary

The device's PROFINET service is vulnerable to a buffer overflow attack due to its default configuration. This vulnerability, tracked as CVE-2025-41769, has a CVSS score of 9.3, indicating a critical severity level. An unauthenticated remote attacker could exploit this vulnerability to either reboot the device or execute arbitrary code. The technical impact of this vulnerability is significant, as it could allow for remote code execution and device manipulation. Organizations should prioritize patching or mitigating this vulnerability to prevent potential exploitation.

Defensive priority

Critical vulnerability in PROFINET service with potential for remote code execution and device reboot.

Recommended defensive actions

  • Review device configuration and PROFINET service setup to identify potential vulnerabilities
  • Implement compensating controls to monitor and restrict access to the affected service
  • Verify vendor remediation and apply patches or updates as available
  • Conduct inventory checks to identify potentially affected devices
  • Monitor for suspicious activity and exception tracking

Evidence notes

Evidence from the official CVE Program record and NVD vulnerability detail page indicates a buffer overflow vulnerability in the device's PROFINET service. The limited information available suggests that the vulnerability exists in the default configuration of the device. Defenders should verify the affected products, review vendor remediation guidance, and monitor for potential exploitation attempts. Further details on affected products and vendor remediation are needed for comprehensive risk assessment.

Sources and references

Verified primary and authoritative sources

  • CVE-2025-41769 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2025-41769

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2025-41769 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2025-41769

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.