# CVE-2026-17615: Resteasy-core: resteasy sourceprovider remote unauthenticated file read

> Unauthenticated attackers can read sensitive files via XML External Entity injection in RESTEasy's SourceProvider when handling XML requests.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Aug 2026
- **Updated:** 28 Oct 2026
- **Also known as:** ALSA-2026:72424, DEBIAN-CVE-2026-17615, GHSA-h82j-45qh-f65r, RHSA-2026:72424, RHSA-2026:77297, RHSA-2026:80505, RLSA-2026:72424, UBUNTU-CVE-2026-17615

## What is CVE-2026-17615?

CVE-2026-17615 is a high-severity vulnerability in Red Hat Build of Apache Camel 3.33.3.SP1, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in RESTEasy's SourceProvider. This vulnerability allows an unauthenticated attacker to perform an unauthenticated remote file read. By sending a specially crafted XML body with a DOCTYPE declaration referencing external entities to an endpoint that accepts application/xml and returns Source or StreamSource, the server can be tricked into resolving the entity and including sensitive file contents in the HTTP response. This is due to the SourceProvider.writeTo() method creating a SAXParser without disabling external entity resolution, leading to an XML External Entity (XXE) vulnerability.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pki-resteasy-client` | AlmaLinux:9 | All versions | 3.0.26-20.el9_8 |
| `pki-resteasy-core` | AlmaLinux:9 | All versions | 3.0.26-20.el9_8 |
| `pki-resteasy-jackson2-provider` | AlmaLinux:9 | All versions | 3.0.26-20.el9_8 |
| `pki-resteasy-servlet-initializer` | AlmaLinux:9 | All versions | 3.0.26-20.el9_8 |
| `pki-resteasy-client` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.0.26-20.el9_8 |
| `pki-resteasy-core` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.0.26-20.el9_8 |
| `pki-resteasy-jackson2-provider` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.0.26-20.el9_8 |
| `pki-resteasy-servlet-initializer` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.0.26-20.el9_8 |
| `resteasy` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.0.26-20.el9_8 |
| `pki-resteasy-client` | Red Hat:rhel_e4s:9.4::appstream | All versions | 0:3.0.26-20.el9_4 |
| `pki-resteasy-core` | Red Hat:rhel_e4s:9.4::appstream | All versions | 0:3.0.26-20.el9_4 |
| `pki-resteasy-jackson2-provider` | Red Hat:rhel_e4s:9.4::appstream | All versions | 0:3.0.26-20.el9_4 |
| `pki-resteasy-servlet-initializer` | Red Hat:rhel_e4s:9.4::appstream | All versions | 0:3.0.26-20.el9_4 |
| `resteasy` | Red Hat:rhel_e4s:9.4::appstream | All versions | 0:3.0.26-20.el9_4 |
| `pki-resteasy-client` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:3.0.26-20.el9_6 |
| `pki-resteasy-core` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:3.0.26-20.el9_6 |
| `pki-resteasy-jackson2-provider` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:3.0.26-20.el9_6 |
| `pki-resteasy-servlet-initializer` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:3.0.26-20.el9_6 |
| `resteasy` | Red Hat:rhel_eus:9.6::appstream | All versions | 0:3.0.26-20.el9_6 |
| `resteasy` | Rocky Linux:9 | All versions | 0:3.0.26-20.el9_8 |

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

Apply the vendor's patch.

## Is CVE-2026-17615 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17615 is a high-severity vulnerability in Red Hat Build of Apache Camel 3.33.3.SP1, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-17615 in the wild and no public exploit code.

Affected product: Red Hat Build of Apache Camel 3.33.3.SP1. 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-17615/ (Markdown: https://insights.sbomify.com/CVE-2026-17615/index.md)
```

## Sources

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

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