CVE-2026-41939
Hard-coded WildFly creds allow unauthenticated RCE via management console.
Is CVE-2026-41939 being exploited?
Not confirmed. CVE-2026-41939 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.80% probability of exploitation in the next 30 days.
How severe is CVE-2026-41939?
CVE-2026-41939 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-41939?
Yes. A fix has been recorded for CVE-2026-41939. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41939 affect?
CVE-2026-41939 affects Care Everywhere Gateway 14.3.10, Bundled WildFly 8.2.0.Final management interface, Windows hosts running the product. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41939?
Upgrade to fixed release, disable/block WildFly management (port 20990), rotate creds, isolate affected hosts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can log into WildFly on port 20990 using default creds, deploy a WAR and achieve remote code execution as the Windows machine account.
Immediate action required
- affected14.3.10
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.