# CVE-2026-115748: Apache Vysper: Authorization bypass


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-whj5-44p4-m2ff

## What is CVE-2026-115748?

CVE-2026-115748 is a high-severity vulnerability in Apache Vysper, published on 26 Oct 2026. 

### Official description

**UNSUPPORTED WHEN ASSIGNED**  Authorization bypass in Apache Vysper, all versions.

Apache Vysper is an XMPP (Jabber) server library. Its XEP-0077 (In-Band Registration) implementation is missing an authentication check, allowing any authenticated user to compromise other accounts.

As this project is retired, we do not plan to release a version that fixes this issue. Users are recommended to find an alternative.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-115748 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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