# CVE-2026-70448: XML external entity in Jenkins Ivy Report Plugin

> Attackers can exploit XML external entity vulnerabilities in the Jenkins Ivy Report Plugin to read sensitive files or cause denial of service.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-64jg-65j7-rrm4

## What is CVE-2026-70448?

CVE-2026-70448 is a high-severity vulnerability in Jenkins Ivy Report Plugin, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins Ivy Report Plugin 1.2 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks when processing Ivy report files.

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

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


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

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

## Is CVE-2026-70448 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-70448 is a high-severity vulnerability in Jenkins Ivy Report Plugin, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-70448 in the wild and no public exploit code.

Affected product: Jenkins Ivy Report Plugin. 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-70448/ (Markdown: https://insights.sbomify.com/CVE-2026-70448/index.md)
```

## Sources

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

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