# CVE-2026-113582: Apache Abdera: XML external entity expansion in Atom document parsing


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-7wc2-gp9g-c8r6

## What is CVE-2026-113582?

CVE-2026-113582 is a high-severity vulnerability in Apache Abdera, published on 22 Oct 2026. 

### Official description

UNSUPPORTED WHEN ASSIGNED Improper restriction of XML external entity references in Apache Abdera allows an attacker to access sensitive data or make server-side requests when an application parses attacker-controlled XML with Abdera.

This issue affects Apache Abdera: all versions.

Apache Abdera is retired and no longer supported, so we do not plan to release a version that fixes this issue. Users are recommended to migrate to a maintained alternative. Applications that cannot migrate should ensure that untrusted XML cannot reach the affected Abdera parser or JDBC adapter parsing paths. Actively maintained downstream products may still be impacted if they include an affected Abdera artifact.

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

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

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


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

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

## Is CVE-2026-113582 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113582 is a high-severity vulnerability in Apache Abdera, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113582 in the wild and no public exploit code.

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

## Sources

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

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