# CVE-2026-41939: Care Everywhere Gateway 14.3.10 Hard-coded Credentials RCE via WildFly

> Attackers can use hard-coded credentials to access the WildFly management console and deploy malicious archives, achieving remote code execution on the host.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-pr7r-jf2h-77g3

## What is CVE-2026-41939?

CVE-2026-41939 is a critical vulnerability in Care Everywhere Gateway, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Care 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.

Weakness: CWE-1392 (Use of Default Credentials)

## Which versions are affected by CVE-2026-41939?


## How do I fix CVE-2026-41939?

No fix has been published for CVE-2026-41939 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-41939 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41939 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41939 and fix it if it is affected.

What it is: CVE-2026-41939 is a critical vulnerability in Care Everywhere Gateway, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41939 exists.

Affected product: Care Everywhere Gateway. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41939/ (Markdown: https://insights.sbomify.com/CVE-2026-41939/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41939
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41939
- OSV: https://osv.dev/vulnerability/CVE-2026-41939

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41939/
Summaries are generated and may contain mistakes; the official description above is the record.