# CVE-2026-119724: Apache JClouds: XML External Entity (XXE) in provider-response parsing


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-fg42-24r3-x39g

## What is CVE-2026-119724?

CVE-2026-119724 is a high-severity vulnerability in Apache JClouds, published on 3 Nov 2026. 

### Official description

** UNSUPPORTED WHEN ASSIGNED ** Improper restriction of recursive entity references in DTDs ('XML entity expansion') vulnerability in Apache JClouds.

This issue affects Apache JClouds: all versions.

As this project is retired, we do not plan to release a version that fixes this issue. Users are recommended to find an alternative or restrict access to the instance to trusted users.

NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-776 (Improper Restriction of Recursive Entity References in DTDs)

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


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

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

## Is CVE-2026-119724 being exploited?

There is no known exploitation of CVE-2026-119724 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119724 is a high-severity vulnerability in Apache JClouds, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-119724 in the wild and no public exploit code.

Affected product: Apache JClouds. 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-119724/ (Markdown: https://insights.sbomify.com/CVE-2026-119724/index.md)
```

## Sources

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

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