dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2025-41659

HIGH · 8.3 CVSS v3.1 Published 2025-08-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
A low-privileged attacker can remotely access the PKI folder of the CODESYS Control runtime system and thus read and write certificates and its keys. This allows sensitive data to be extracted or to accept certificates as trusted. Although all services remain available, only unencrypted communication is possible if the certificates are deleted.

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 · high confidence

A low-privileged attacker can remotely access the PKI folder in CODESYS Control runtime systems, allowing read/write access to certificates and private keys. This enables extraction of sensitive cryptographic material or injection of malicious certificates to establish trusted connections. If certificates are deleted, only unencrypted communication remains possible.

MitigationRestrict access to the PKI folder through proper file system permissions and implement authentication/authorization checks for PKI operations to prevent unauthorized access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify CODESYS Control is installed
    Locate the CODESYS installation directory (commonly C:\Program Files\CODESYS or /usr/lib/codesys on Linux) and check for the presence of the CODESYS Control runtime. Check version by examining the installed software or running 'codesysinfo' command if available.
    Affected if CODESYS Control runtime is installed and the version falls within the affected range (if known)
  2. Locate the PKI folder
    Navigate to the CODESYS installation directory and search for a folder named 'PKI', 'pki', or 'Certificates'. This folder typically resides under the runtime's data directory (for example, C:\ProgramData\CODESYS\Control\PKI or /var/lib/codesys/control/pki).
    Affected if The PKI folder exists in the CODESYS installation or data directory
  3. Check PKI folder permissions
    On Windows, right-click the PKI folder, select Properties > Security tab, and review the permissions for users/groups. On Linux, run 'ls -la' or 'getfacl' on the PKI folder to inspect read/write permissions for non-admin users.
    Affected if Users other than administrators or the system account have Read or Write permissions to the PKI folder
  4. Inspect PKI folder contents
    List the contents of the PKI folder to confirm the presence of certificate files (.cer, .crt, .pem) and private key files (.key, .pem). On Windows use 'dir' command; on Linux use 'ls -la'.
    Affected if Certificate and private key files are present and accessible to unauthorized users
  5. Test unauthorized access
    Attempt to read or copy files from the PKI folder using a low-privileged account (a standard user account without administrator rights). Also attempt to write new files into the folder.
    Affected if A low-privileged user can successfully read certificate/key files or write new files into the PKI folder

If CODESYS Control runtime is installed and the PKI folder grants read or write access to non-administrative users, the system is vulnerable to CVE-2025-41659.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access to the PKI folder through proper file system permissions and implement authentication/authorization checks for PKI operations to prevent unauthorized access.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41659 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-41659 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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