CVE-2026-41939
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 · uneditedCare Everywhere Gateway 14.3.10 contains a hard-coded credentials vulnerability in the bundled WildFly 8.2.0.Final management interface that allows unauthenticated remote attackers to gain administrative access by using default credentials identical across all installations. Attackers can authenticate to the exposed WildFly management console on port 20990 and deploy a malicious Web Application Archive file through the Deployments interface to achieve remote code execution as the Windows machine account. Version 14.x.x was declared end-of-life (EOL) in 2017 and future releases have addressed the vulnerable finding.
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 confidenceCare Everywhere Gateway 14.3.10 bundles WildFly 8.2.0.Final with hard-coded default credentials in its management interface on port 20990. Unauthenticated remote attackers can leverage these identical credentials across all installations to access the WildFly admin console, upload and deploy malicious WAR files, and achieve remote code execution as the Windows machine account.
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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Care Everywhere Gateway installationLook for the Care Everywhere Gateway installation directory (commonly in Program Files or a dedicated application folder) and check for running processes named 'CareEverywhereGateway' or similarAffected if Care Everywhere Gateway is installed and the installation cannot be verified as a post-vulnerable version
-
Check installed versionLocate version information in the installation directory (typically in a version.txt, about dialog, or configuration files) and compare to 14.3.10Affected if Installed version is 14.3.10 or lower (pre-fix version)
-
Verify bundled WildFly versionWithin the Care Everywhere Gateway installation directory, locate the WildFly subdirectory and check the version file or jar manifest for '8.2.0.Final'Affected if Bundled WildFly version is 8.2.0.Final
-
Check if management port 20990 is listeningRun 'netstat -an | findstr 20990' or 'Get-NetTCPConnection -LocalPort 20990' to determine if the WildFly management interface port is open and listeningAffected if Port 20990 is in LISTENING state on any interface
-
Verify network exposure of port 20990Confirm port 20990 is bound to non-localhost interfaces (0.0.0.0 or external IP rather than 127.0.0.1) indicating the management interface is network-accessibleAffected if Port 20990 is listening on 0.0.0.0 or an external IP address rather than localhost only
Environment is affected if Care Everywhere Gateway version 14.3.10 or lower (with WildFly 8.2.0.Final) is installed AND port 20990 is exposed on the network, enabling unauthenticated attackers to reach the management interface with default credentials.
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 · scopedUpgrade from EOL version 14.x to a supported release that addresses this finding. As an interim control, block external access to port 20990 at the network perimeter until the upgrade is completed.
Contact vendor for specific supported version (14.x was EOL in 2017; newer releases contain the fix)
- 1. Contact NextGen Healthcare or the Care Everywhere Gateway vendor to obtain the specific fixed release version that addresses CVE-2026-41939
- 2. Request documentation on the migration path from the EOL 14.x version to a supported release
- 3. Before upgrading, perform a complete backup of the Care Everywhere Gateway system and database
- 4. Schedule a maintenance window as the upgrade will likely require downtime
- 5. Upgrade the Care Everywhere Gateway to the vendor-specified supported version that includes the fix for hard-coded credentials in WildFly
- 6. After upgrade, verify that the WildFly management console (port 20990) is either disabled, bound to localhost only, or protected with strong non-default credentials
- 7. Change any default passwords that may have been present in the WildFly or application configuration
- 8. Test all critical workflows to ensure the upgrade did not break existing functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41939 — 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-41939 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