dbcve.org
Control For Beaglebone SlApplication · Codesys

CVE-2025-41738

HIGH · 7.5 CVSS v3.1 Published 2025-12-01
Fix available
A fix is available. Upgrade to 4.19.0.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
An unauthenticated remote attacker may cause the visualisation server of the CODESYS Control runtime system to access a resource with a pointer of wrong type, potentially leading to a denial-of-service (DoS) condition.

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

The vulnerability exists in the CODESYS Control runtime system's visualization server component. An unauthenticated remote attacker can trigger the server to access a resource using an incorrectly typed pointer, causing a type confusion error that leads to a denial-of-service condition.

MitigationApply vendor-supplied patches for CODESYS Control when available; if no patch exists, consider disabling or isolating the visualization server from untrusted networks to reduce exposure.

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
Control For Beaglebone SlApplication
Affected:>= 4.5.0.0, < 4.19.0.0
Control For Empc A\/imx6 SlApplication
Affected:>= 4.5.0.0, <= 4.19.0.0
Control For Iot2000 SlApplication
Affected:>= 4.5.0.0, < 4.19.0.0
Control For Linux Arm SlApplication
Affected:>= 4.5.0.0, < 4.19.0.0
Control For Linux SlApplication
Affected:>= 4.5.0.0, < 4.19.0.0
Control For Pfc100 SlApplication
Affected:>= 4.5.0.0, <= 4.19.0.0
Control For Pfc200 SlApplication
Affected:>= 4.5.0.0, < 4.19.0.0
Control For Plcnext SlApplication
Affected:>= 4.5.0.0, < 4.19.0.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

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

  1. Identify the installed CODESYS Control product
    Locate the CODESYS Control runtime package on the system and note the specific product name (e.g., Codesys Control For Beaglebone Sl, Codesys Control For Linux Sl, etc.)
    Affected if The product matches one of the affected products listed in the CVE advisory
  2. Check the installed version number
    Retrieve the version of the installed CODESYS Control product using the runtime system's version check mechanism or system information
    Affected if The version falls within the affected range: >= 4.5.0.0 and < 4.19.0.0 (or <= 4.19.0.0 depending on the specific product variant)
  3. Confirm the visualization server component is enabled
    Inspect the CODESYS Control runtime configuration to determine whether the visualization server feature is active
    Affected if The visualization server is enabled and running as part of the runtime system
  4. Assess network exposure of the visualization server
    Review network configuration and firewall settings to determine if the visualization server port is accessible from untrusted networks
    Affected if The visualization server is exposed to untrusted or public networks without authentication barriers

The environment is affected if the installed CODESYS Control product version is between 4.5.0.0 and 4.19.0.0 (exclusive or inclusive depending on product) and the visualization server component is enabled and network-accessible.

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.

dbcve · scoped
Upgrade available Upgrade to 4.19.0.0 or later
Fixed in 4.19.0.0
Interim mitigation

Apply vendor-supplied patches for CODESYS Control when available; if no patch exists, consider disabling or isolating the visualization server from untrusted networks to reduce exposure.

Recommended fix Moderate confidence

CODESYS Control runtime version 4.19.0.0 or later

  1. 1. Identify the specific CODESYS Control product in use from the affected product list
  2. 2. Download the CODESYS Control runtime version 4.19.0.0 or later from the official vendor source (codesys.com)
  3. 3. Create a backup of the current runtime configuration and project files
  4. 4. Follow the vendor's standard upgrade procedure to install version 4.19.0.0 or newer
  5. 5. Verify the visualization server starts correctly after upgrade
  6. 6. Test that the visualization functionality operates normally

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Control For Beaglebone Sl Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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