Apache Vysper Unbounded Allocation

Apache Vysper

Apache Vysper has an unbounded allocation vulnerability in XML parsing, allowing attackers to cause an out-of-memory condition.

Do this now

Restrict network access to Apache Vysper XML parsing endpoints and monitor memory use until a fix is released.

First seen: 23 Oct 2026
Last update: 23 Oct 2026, 13:48 UTC
Identifiers: CVE-2026-115721 ID not published yet
CVE-2026-115748 ID not published yet
Source: news
On the menu as: Java

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## Apache Vysper Unbounded Allocation
Severity: unknown. Patch status: no fix yet.
Affected: Apache Vysper
Ids: CVE-2026-115721, CVE-2026-115748

Apache Vysper has an unbounded allocation vulnerability in XML parsing, allowing attackers to cause an out-of-memory condition.

## Steps
1. Search the repo, its CI and infra config for Apache Vysper. If present, report the version in use and whether it's affected.
2. There is no fix yet. Until one ships: Apache Vysper has an unbounded allocation vulnerability in XML parsing, allowing attackers to cause an out-of-memory condition.

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve("CVE-2026-115721") for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://seclists.org/oss-sec/2026/q4/356 https://seclists.org/oss-sec/2026/q4/357
https://pwned.coffee/i/apache-vysper-unbounded-allocation-cve-2026-115721

Receipt

Exploitation: No known exploitation
Score: No CVSS published yet: severity unknown.
Last checked: 24 Oct 2026, 17:17 UTC

Sources: KEV – CVE record – Vendor –

Sources

Totalone coffee