CVE-2025-41769: Unauthenticated Buffer Overflow in PROFINET Service
Noroxi assessment
Priority: Monitor (action score 37/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.83% (FIRST EPSS); higher than 57.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Phoenix Contact AXC F 1152 2026.0.3; Phoenix Contact AXC F 1252 2026.0.3; Phoenix Contact AXC F 2152 2026.0.3.
Low priority for now. Upgrade to Phoenix Contact AXC F 1152 2026.0.3; Phoenix Contact AXC F 1252 2026.0.3; Phoenix Contact AXC F 2152 2026.0.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The device's PROFINET service is affected by a buffer overflow vulnerability that exists in the default configuration. An unauthenticated remote attacker could exploit this vulnerability to reboot the device or execute arbitrary code.
- Published
- Aug 12, 2026
- Updated
- Sep 29, 2026
- EPSS
- 0.8% · 57th percentile
- CWE
- CWE-120
Report tools
Action score
37
Monitor
Low priority for now.
- CVSS
- 37 / 40 · 9.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · CERTVDE
- 9.3
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (CERTVDE). Independent of NVD's CPE analysis and usually ahead of it.
Phoenix Contact AXC F 1152
- 2019.0.4 and later · before 2026.0.3affected · semver
Phoenix Contact AXC F 1252
- 2019.0.4 and later · before 2026.0.3affected · semver
Phoenix Contact AXC F 2152
- 2019.0.4 and later · before 2026.0.3affected · semver
Phoenix Contact AXC F 3152
- 2019.0.4 and later · before 2026.0.3affected · semver
Phoenix Contact BPC 9102S
- 2019.0.4 and later · before 2026.0.3affected · semver
Phoenix Contact BPC 9202S
- 2019.0.4 and later · before 2026.0.3affected · semver
Phoenix Contact EPC 1502
- 2019.0.4 and later · before 2026.0.3affected · semver
Phoenix Contact EPC 1522
- 2019.0.4 and later · before 2026.0.3affected · semver
Phoenix Contact RFC 4072R
- 2019.0.4 and later · before 2026.0.3affected · semver
Phoenix Contact RFC 4072S
- 2019.0.4 and later · before 2026.0.3affected · semver
Phoenix Contact VL3 UPC 2440 EDGE
- 2019.0.4 and later · before 2026.0.3affected · semver
Phoenix Contact VPLCNEXT CONTROL 1000
- 2019.0.4 and later · before 2026.0.3affected · semver
Same product
phoenix contact: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-41668Phoenix Contact: File access due to the replacement of a critical file used by the service security-profile35Monitor
- CVE-2025-41667Phoenix Contact: File access due to the replacement of a critical file used by the arp-preinit script35Monitor
- CVE-2025-41666Phoenix Contact: File access due to the replacement of a critical file used by the watchdog35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-41669May 27, 2026 · Insufficient Verification of Data Authenticity34Monitor
- ← EarlierCVE-2025-41670May 27, 2026 · Untrusted Search Path34Monitor
- Later →CVE-2025-41770Aug 12, 2026 · Unauthenticated Denial of Service34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Phoenix Contact AXC F 1152 | 2026.0.3 | Vendor (CNA) |
| Phoenix Contact AXC F 1252 | 2026.0.3 | Vendor (CNA) |
| Phoenix Contact AXC F 2152 | 2026.0.3 | Vendor (CNA) |
| Phoenix Contact AXC F 3152 | 2026.0.3 | Vendor (CNA) |
| Phoenix Contact BPC 9102S | 2026.0.3 | Vendor (CNA) |
| Phoenix Contact BPC 9202S | 2026.0.3 | Vendor (CNA) |
| Phoenix Contact EPC 1502 | 2026.0.3 | Vendor (CNA) |
| Phoenix Contact EPC 1522 | 2026.0.3 | Vendor (CNA) |
| Phoenix Contact RFC 4072R | 2026.0.3 | Vendor (CNA) |
| Phoenix Contact RFC 4072S | 2026.0.3 | Vendor (CNA) |
| Phoenix Contact VL3 UPC 2440 EDGE | 2026.0.3 | Vendor (CNA) |
| Phoenix Contact VPLCNEXT CONTROL 1000 | 2026.0.3 | Vendor (CNA) |
| Phoenix Contact VPLCNEXT CONTROL 2000 | 2026.0.3 | Vendor (CNA) |
| Phoenix Contact VPLCNEXT CONTROL 3000 | 2026.0.3 | Vendor (CNA) |
| Phoenix Contact VPLCNEXT CONTROL 500 | 2026.0.3 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- CyberDanubefinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];
memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];
if (pkt->len > sizeof(buf)) {
return -EINVAL;
}
memcpy(buf, pkt->data, pkt->len);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.