CVE-2026-0393
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 may expose credentials remotely between low privileged visualization users during concurrent login operations due to insufficient isolation of authentication data. The vulnerability affects only login operations within an active visualization session.
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 confidenceDuring concurrent login operations within an active visualization session, authentication credentials from one low-privileged user may be exposed to other users due to insufficient isolation of authentication data in memory or session handling. This is a race condition or improper session isolation flaw specific to visualization login operations.
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>= 1.0.0.0, < 4.10.0.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Codesys Visualization versionLocate the installed Codesys Visualization component and retrieve its version number from the product information, About dialog, or system registry if applicableAffected if Installed version falls within >= 1.0.0.0 and < 4.10.0.0 range
-
Confirm Visualization component is in useVerify that the Codesys Visualization module or runtime component is installed and active in the environmentAffected if Codesys Visualization is installed and operational
-
Check for multi-user visualization environmentExamine whether concurrent user sessions are possible or configured in the visualization environment (e.g., multiple clients, terminal services, or multi-user runtime access)Affected if Multiple users can access the visualization environment simultaneously or concurrently
-
Review visualization login session isolationInspect the runtime configuration or session management settings for the visualization component to determine if authentication data isolation between concurrent sessions is enforcedAffected if Session isolation is not properly configured or credential data may be shared between concurrent users
User is affected if Codesys Visualization version is >= 1.0.0.0 and < 4.10.0.0, the visualization component is active, and multiple users can access concurrent sessions where authentication data may not be properly isolated between users.
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.
dbcve · scoped4.10.0.0
Implement proper session isolation to ensure each concurrent login operation maintains separate authentication data, preventing credential leakage between user sessions.
4.10.0.0 or later
- 1. Identify all CODESYS Visualization installations in the environment running versions >= 1.0.0.0 and < 4.10.0.0
- 2. Plan maintenance window for upgrade procedure
- 3. Backup current visualization configuration and project files
- 4. Download CODESYS Visualization version 4.10.0.0 or later from official vendor source
- 5. Stop all active visualization sessions and services
- 6. Install version 4.10.0.0 or newer following vendor installation guidelines
- 7. Restore configuration from backup if needed
- 8. Verify visualization login functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0393 — 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-0393 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