# CVE-2026-54224: Denial of Service in UBB.threads

> An authenticated attacker can cause a denial of service in UBB.threads by exhausting database resources through concurrent profile view requests.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA: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:** 18 Jun 2026
- **Updated:** 18 Jun 2026
- **Also known as:** GHSA-r4cc-xcx2-vp28

## What is CVE-2026-54224?

CVE-2026-54224 is a high-severity denial of service vulnerability in UBB.threads, published on 18 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

UBB.threads is vulnerable to Denial of Service (DoS). By sending multiple concurrent requests to view any user profile on instances with many registered users, an authenticated attacker can easily exhaust database resources and completely deny access to the application for other users.
Because vendor contact attempts were unsuccessful, the vulnerability has only been confirmed in version 7.7.5 but may also affect other versions.

Weakness: CWE-405 (Asymmetric Resource Consumption (Amplification))

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


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

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

## Is CVE-2026-54224 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54224 is a high-severity denial of service vulnerability in UBB.threads, published on 18 Jun 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-54224 in the wild and no public exploit code.

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

## Sources

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

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