# CVE-2026-33541: TSPortal's Uncontrolled User Creation via Validation Side Effects Leads to Potential Denial of Service

> Attackers can create arbitrary user records via validation side effects, causing uncontrolled database growth and potential denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 27 Mar 2026
- **Also known as:** GHSA-f346-8rp3-4h9h

## What is CVE-2026-33541?

CVE-2026-33541 is a medium-severity denial of service vulnerability in miraheze TSPortal, published on 26 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TSPortal is the WikiTide Foundation’s in-house platform used by the Trust and Safety team to manage reports, investigations, appeals, and transparency work. Prior to version 34, a flaw in TSPortal allowed attackers to create arbitrary user records in the database by abusing validation logic. While validation correctly rejected invalid usernames, a side effect within a validation rule caused user records to be created regardless of whether the request succeeded. This could be exploited to cause uncontrolled database growth, leading to a potential denial of service (DoS). Version 34 contains a fix for the issue.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption)

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

2 open source packages ship an affected version, including miraheze/ts-portal. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `miraheze/ts-portal` | Packagist | All versions | 34 |
| `miraheze/ts-portal` | Packagist | All versions | 34 |

Products: Wikitide Tsportal.

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

Upgrade miraheze/ts-portal to 34 or later.

## Is CVE-2026-33541 being exploited?

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

## Other vulnerabilities in miraheze TSPortal

- [CVE-2026-29788](https://insights.sbomify.com/CVE-2026-29788/): TSPortal: Anyone can forge self-deletion requests of any user (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33541 is a medium-severity denial of service vulnerability in miraheze TSPortal, published on 26 Mar 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-33541 in the wild and no public exploit code.

Affected packages and fixed versions:
- miraheze/ts-portal (Packagist): affected all versions; fixed in 34
- miraheze/ts-portal (Packagist): affected all versions; fixed in 34

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-33541/ (Markdown: https://insights.sbomify.com/CVE-2026-33541/index.md)
```

## Sources

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

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