dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-23746

CRITICAL · 9.3 CVSS v4.0 Published 2026-01-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Entrust Instant Financial Issuance (IFI) On Premise software (formerly referred to as CardWizard) versions 5.x, prior to 6.10.5, and prior to 6.11.1 contain an insecure .NET Remoting exposure in the SmartCardController service (DCG.SmartCardControllerService.exe). The service registers a TCP remoting channel with unsafe formatter/settings that permit untrusted remoting object invocation. A remote, unauthenticated attacker who can reach the remoting port can invoke exposed remoting objects to read arbitrary files from the server and coerce outbound authentication, and may achieve arbitrary file write and remote code execution via known .NET Remoting exploitation techniques. This can lead to disclosure of sensitive installation and service-account data and compromise of the affected host.

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

Entrust Instant Financial Issuance (IFI) On Premise software contains an insecure .NET Remoting exposure in the SmartCardController service. The service registers a TCP remoting channel with unsafe formatter/settings that permit unauthenticated remote attackers to invoke exposed remoting objects, enabling arbitrary file read, outbound authentication coercion, and potentially arbitrary file write and remote code execution.

MitigationUpgrade to version 6.10.5 or later, or 6.11.1 or later. If immediate upgrade is not feasible, block or restrict network access to the remoting TCP port via firewall or network segmentation.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Entrust IFI installation exists
    Check for Entrust Instant Financial Issuance software by searching for installation directories (commonly under C:\Program Files\Entrust\ or C:\Program Files (x86)\Entrust\), or look for the SmartCardController Windows service using 'services.msc' or 'sc query' command.
    Affected if The software is installed and the SmartCardController service is present.
  2. Determine installed IFI version
    Check the installed version by examining the SmartCardController service executable properties (right-click the service binary, view Details tab for File Version), or check Add/Remove Programs for the Entrust IFI version entry.
    Affected if The version is lower than 6.10.5 or between 6.11.0 and 6.11.1 (exclusive).
  3. Confirm SmartCardController service is running
    Open Services (services.msc) and verify the SmartCardController service status, or run 'sc query SmartCardController' from an elevated command prompt.
    Affected if The SmartCardController service is in a Running state.
  4. Identify the .NET Remoting TCP listener port
    Run 'netstat -anob' or use Process Explorer to identify which TCP port the SmartCardController service is listening on. .NET Remoting typically binds to a specific TCP port configured in the service configuration.
    Affected if The SmartCardController service has an open TCP listening port exposed on the network.
  5. Verify network accessibility of the remoting port
    From a remote system, attempt a TCP connection to the identified port (e.g., using PowerShell 'Test-NetConnection -ComputerName <target> -Port <port>' or telnet). Also verify if the port is bound to 0.0.0.0 (all interfaces) vs 127.0.0.1 (localhost only).
    Affected if The remoting TCP port is accessible from untrusted network segments (not restricted to localhost or trusted management networks).

A user is affected if Entrust IFI with a version below 6.10.5 (or between 6.11.0 and 6.11.1) is installed, the SmartCardController service is running, and the .NET Remoting TCP port is 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 6.10.5 or later, or 6.11.1 or later. If immediate upgrade is not feasible, block or restrict network access to the remoting TCP port via firewall or network segmentation.

Recommended fix Moderate confidence

Upgrade to version 6.10.5 or 6.11.1 (or later) - 6.11.1 is the preferred target as it represents the newer stable release

  1. 1. Identify the currently installed version of Entrust Instant Financial Issuance (IFI) / CardWizard software
  2. 2. If running version 5.x, plan upgrade path to version 6.10.5 or 6.11.1 (or later)
  3. 3. If running version 6.x prior to 6.10.5 or 6.11.1, upgrade to version 6.10.5 or 6.11.1 (or later)
  4. 4. Prior to upgrade, backup all configuration files, databases, and installation directories
  5. 5. Test the upgrade in a non-production environment to verify functionality
  6. 6. Schedule maintenance window for production upgrade
  7. 7. After upgrade, verify the SmartCardController service (DCG.SmartCardControllerService.exe) is running securely
  8. 8. Confirm .NET Remoting port is not exposed to untrusted networks or implement proper network segmentation
Caveat Review release notes for 6.10.5 and 6.11.1 for any configuration changes or feature modifications before upgrading; test thoroughly in staging environment

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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