# CVE-2026-72605: Swing Music Swing Music - Missing Authentication

> Unauthenticated attackers can create arbitrary user accounts via an allowlisted endpoint, gaining access to protected server functionality.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-j8m4-xpvr-6gcw

## What is CVE-2026-72605?

CVE-2026-72605 is a high-severity missing authorization vulnerability in Swing Music, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A missing authentication vulnerability in Swing Music 3.0.0 allows unauthenticated remote attackers to create arbitrary user accounts via the POST /auth/profile/create endpoint. The endpoint is allowlisted from JWT verification, permitting unauthenticated account creation. An attacker can register an account and use it to access protected functionality on the server.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-72605 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72605 is a high-severity missing authorization vulnerability in Swing Music, published on 11 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-72605 in the wild and no public exploit code.

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

## Sources

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

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