CVE-2026-44108: Firewall bypass during shutdown
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 58.1% 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 CHARX SEC-3000 1.9.1; Phoenix Contact CHARX SEC-3050 1.9.1; Phoenix Contact CHARX SEC-3100 1.9.1.
Low priority for now. Upgrade to Phoenix Contact CHARX SEC-3000 1.9.1; Phoenix Contact CHARX SEC-3050 1.9.1; Phoenix Contact CHARX SEC-3100 1.9.1 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
Due to a flaw in the execution order of scripts during shutdown, the firewall is terminated prematurely during system shutdown. This creates a temporary window in which internal services may become externally accessible, potentially allowing an unauthenticated remote attacker to connect to these services, resulting in full system compromise.
- Published
- Jul 30, 2026
- Updated
- Jul 30, 2026
- EPSS
- 0.8% · 58th percentile
- CWE
- CWE-696
Report tools
Action score
37
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.
Is your version affected? Check itNoroxi 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 CHARX SEC-3000
- 1.0.0 and later · before 1.9.1affected · semver
Phoenix Contact CHARX SEC-3050
- 1.0.0 and later · before 1.9.1affected · semver
Phoenix Contact CHARX SEC-3100
- 1.0.0 and later · before 1.9.1affected · semver
Phoenix Contact CHARX SEC-3150
- 1.0.0 and later · before 1.9.1affected · semver
Same product
phoenix contact: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-7849Command Injection in SCM (idledisconnect parameter)37Monitor
- CVE-2026-44104ControllerAgent does not perform validation of firmware37Monitor
- CVE-2026-44101OCPP reconfiguration vulnerability37Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-44105Jul 30, 2026 · Cleartext password in logs23Monitor
- ← EarlierCVE-2026-44107Jul 30, 2026 · Exposed Reboot via Modbus34Monitor
- Later →CVE-2026-44093Jul 30, 2026 · Local Privilege Escalation vulnerability in /etc/init.d/user-applications via user-application start script34Monitor
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 CHARX SEC-3000 | 1.9.1 | Vendor (CNA) |
| Phoenix Contact CHARX SEC-3050 | 1.9.1 | Vendor (CNA) |
| Phoenix Contact CHARX SEC-3100 | 1.9.1 | Vendor (CNA) |
| Phoenix Contact CHARX SEC-3150 | 1.9.1 | 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).
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- ZDIfinder
Not on record for this CVE: patch commit or PR link · variant or chain candidate · public bounty program.
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-696 · Incorrect Behavior OrderCVSS 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
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)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.