CVE-2025-41670

Local privilege escalation via user-writable search locations

Published May 27, 2026 · Updated May 27, 2026

Uncontrolled search path handling in Phoenix Contact PLCnext firmware before 2026.0.3 allows local users to gain elevated privileges. An unnamed privileged system service processes configuration or application-related files from filesystem locations writable by low-privileged users. Exploitation requires local low-privilege access and permits influence over the elevated service; Phoenix Contact has not disclosed the service, file names, or exact search sequence.

CVSS severity7.8
High
EPSS probability0.19%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Uncontrolled search path handling in Phoenix Contact PLCnext firmware before 2026.0.3 allows local users to gain elevated privileges. An unnamed privileged system service processes configuration or application-related files from filesystem locations writable by low-privileged users. Exploitation requires local low-privilege access and permits influence over the elevated service; Phoenix Contact has not disclosed the service, file names, or exact search sequence.

The record

CVE
CVE-2025-41670
Published
May 27, 2026
Updated
May 27, 2026
Vendor
Phoenix Contact
Product
BPC 9102S
Classifications
CWE-427, T1574
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 27, 2026CVE publishedPublication date reported by the CVE source.
  2. May 27, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0.0.0 <2026.0.3

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Phoenix Contact · BPC 9102Sversion=0.0.0 <2026.0.3
Phoenix Contact · AXC F 1252version=0.0.0 <2026.0.3
Phoenix Contact · RFC 4072Rversion=0.0.0 <2026.0.3
Phoenix Contact · AXC F 3152version=0.0.0 <2026.0.3
Phoenix Contact · VPLCNEXT CONTROL 2000version=0.0.0 <2026.0.3
Phoenix Contact · EPC 1522version=0.0.0 <2026.0.3
Phoenix Contact · RFC 4072Sversion=0.0.0 <2026.0.3
Phoenix Contact · VPLCNEXT CONTROL 1000version=0.0.0 <2026.0.3
Phoenix Contact · AXC F 2000 EAversion=0.0.0 <2026.0.3
Phoenix Contact · VPLCNEXT CONTROL 500version=0.0.0 <2026.0.3
Phoenix Contact · AXC F 1152version=0.0.0 <2026.0.3
Phoenix Contact · VPLCNEXT CONTROL 3000version=0.0.0 <2026.0.3
Phoenix Contact · VL3 UPC 2440 EDGEversion=0.0.0 <2026.0.3
Phoenix Contact · AXC F 2152version=0.0.0 <2026.0.3

Published CVSS scores

7.8CERT@VDECVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-427Uncontrolled Search Path Element
T1574Hijack Execution Flow

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo