CVE-2026-44468
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe affected product creates a directory with insecure default permissions during administrative installation. This allows a low-privileged local attacker to modify a temporary file defining the components to be installed, enabling local privilege escalation by forcing the deployment of arbitrary components.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe affected product creates a directory with insecure default permissions during administrative installation. A low-privileged local attacker can modify a temporary file that defines which components will be installed, allowing them to force installation of arbitrary components and achieve local privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.5.22.20CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Codesys Development System is installedCheck for Codesys installation by searching for the product in system program directories or registry (Windows: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall, or look in C:\Program Files\3S Software or similar paths).Affected if Codesys Development System is found on the system
-
Check installed version against affected rangeLocate and read the version information (typically in About or Help menu of the application, or check installer logs/product metadata). Compare the version number to 3.5.22.20.Affected if Installed version is lower than 3.5.22.20
-
Identify the administrative installation directoryCheck the installation location used when Codesys was installed with administrative/elevated privileges. Common locations include the installation root directory or a designated component staging directory created during setup.Affected if A Codesys installation directory exists from a prior administrative install
-
Inspect directory permissions for insecurityUse OS-native commands to examine the permissions on the identified installation directory (Windows: right-click > Properties > Security, or run icacls in Command Prompt). Look for Everyone, Users, or other broad group permissions with Write or Modify access.Affected if The directory grants Write or Modify permissions to non-privileged users or groups such as Everyone or Users
-
Check for modifiable temporary installation filesSearch the installation directory for temporary files related to component selection or installation configuration (common patterns include *.tmp, install*.xml, or component manifest files). Verify write permissions on these files.Affected if Temporary installation configuration files are present and writable by low-privileged users
Affected if Codesys Development System version below 3.5.22.20 is installed with an administrative installation directory that has insecure permissions allowing low-privileged users to modify component installation files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data3.5.22.20
Fix the default directory permissions during administrative installation and ensure temporary installation files are protected from unauthorized modification by low-privileged users.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44468 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-44468 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data