dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-41658

MEDIUM · 5.5 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 →
57/100
Remediation priority · Elevated
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
CODESYS Runtime Toolkit-based products may expose sensitive files to local low-privileged operating system users due to default file permissions.

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 confidence

CODESYS Runtime Toolkit-based products have default file permissions that allow local low-privileged operating system users to read sensitive files that should be restricted. This is a local information disclosure vulnerability where sensitive configuration, credentials, or runtime data files are accessible to unprivileged users due to overly permissive default access controls.

MitigationReview and restrict file permissions on sensitive files and directories within the CODESYS Runtime Toolkit installation to ensure only authorized privileged users or processes can access them. Apply the principle of least privilege to file system access controls.

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

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

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. Locate CODESYS Runtime Toolkit installation directory
    Search for common CODESYS installation paths such as C:\Program Files\CODESYS or /opt/codesys, and check for directories named 'CODESYS' or containing 'Runtime' in the program files or installation folders.
    Affected if CODESYS Runtime Toolkit is installed and the installation directory exists on the system.
  2. Identify sensitive configuration and credential files
    Within the CODESYS installation directory, look for files with extensions such as .xml, .cfg, .ini, .xml, .json, .key, .pem, .crt, or files named config, settings, credentials, passwords, or plc logic files (*.project, *.library).
    Affected if Sensitive configuration files, credential files, or runtime data files exist within the CODESYS installation directory.
  3. Check file permissions on sensitive files
    Use OS-native commands: on Windows run 'icacls <file>' or right-click properties > Security tab; on Linux run 'ls -la <file>' or 'getfacl <file>'. Examine which users or groups have Read access.
    Affected if File permissions show that unprivileged users (such as Users group on Windows, or world/others on Linux) have Read permissions on sensitive files.
  4. Verify unprivileged user access to sensitive files
    If possible, attempt to read the sensitive files using a low-privileged test account or by running commands as a standard user (e.g., 'runas /user:StandardUser type <file>' on Windows or 'su - standarduser -c "cat <file>"' on Linux).
    Affected if A low-privileged operating system user can successfully open and read files containing configuration, credentials, or runtime data.
  5. Compare installed version to any known affected versions
    Check the CODESYS product version by looking for version information in the installation directory, registry (Windows), or by running 'codesys --version' if available. Compare against vendor advisory if version ranges become available.
    Affected if The installed version falls within any version range the vendor identifies as affected (when such information becomes available).

A user is affected if CODESYS Runtime Toolkit is installed and unprivileged local users can read sensitive configuration, credential, or runtime data files due to overly permissive default file permissions.

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

Review and restrict file permissions on sensitive files and directories within the CODESYS Runtime Toolkit installation to ensure only authorized privileged users or processes can access them. Apply the principle of least privilege to file system access controls.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41658 — 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-41658 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