# GHSA-8pcw-h6w9-h46g: plone.app.contenttypes has a Denial of Service in File Upload due to excessive filename length

> An attacker with content creation privileges can cause denial of service by uploading files with excessively long filenames, making the UI unresponsive.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Sep 2026

## What is GHSA-8pcw-h6w9-h46g?

GHSA-8pcw-h6w9-h46g is a denial of service vulnerability in plone-app-contenttypes, published on 23 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

### Impact
When creating an Image or File with a very large filename, Plone can become unresponsive. Even if the content loads, it can be hard to edit or delete, because the UI is unwieldy.

### Patches
The problem has been patched in `plone.app.contenttypes`.

* On Plone 6.2, upgrade to `plone.app.contenttypes ` 5.0.1.
* On Plone 6.1, upgrade to `plone.app.contenttypes ` 4.0.10.
* On Plone 6.0, upgrade to `plone.app.contenttypes ` 3.0.12

Another part of this problem has been patched in `plone.app.dexterity`. See [this advisory](https://github.com/plone/plone.app.dexterity/security/advisories/GHSA-5426-92w4-wvhv).

### Workarounds
There are no known workarounds.

This problem was responsibly reported by Aldin Visnjic to the [Plone/Zope Security Team](mailto:security@plone.org). Thank you!

Note: The Plone/Zope Security team felt that the kind of fixes that were needed could be disruptive in corner cases if they were not careful. So they decided to develop the fixes publicly, giving the whole community the chance the review, and giving them the benefit from early feedback.

## Which versions are affected by GHSA-8pcw-h6w9-h46g?

6 open source packages ship an affected version, including plone-app-contenttypes and plone.app.contenttypes.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `plone-app-contenttypes` | PyPI | All versions | 3.0.12 |
| `plone-app-contenttypes` | PyPI | From 4.0.0 | 4.0.10 |
| `plone-app-contenttypes` | PyPI | From 5.0.0 | 5.0.1 |
| `plone.app.contenttypes` | PyPI | All versions | 3.0.12 |
| `plone.app.contenttypes` | PyPI | From 4.0.0 | 4.0.10 |
| `plone.app.contenttypes` | PyPI | From 5.0.0 | 5.0.1 |

## How do I fix GHSA-8pcw-h6w9-h46g?

Upgrade plone-app-contenttypes to a fixed version for your release line: 3.0.12, 4.0.10 or 5.0.1.

## Is GHSA-8pcw-h6w9-h46g being exploited?

There is no known exploitation of GHSA-8pcw-h6w9-h46g in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-8pcw-h6w9-h46g and fix it if it is affected.

What it is: GHSA-8pcw-h6w9-h46g is a denial of service vulnerability in plone-app-contenttypes, published on 23 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-8pcw-h6w9-h46g in the wild and no public exploit code.

Affected packages and fixed versions:
- plone-app-contenttypes (PyPI): affected all versions; fixed in 3.0.12
- plone-app-contenttypes (PyPI): affected from 4.0.0; fixed in 4.0.10
- plone-app-contenttypes (PyPI): affected from 5.0.0; fixed in 5.0.1
- plone.app.contenttypes (PyPI): affected all versions; fixed in 3.0.12
- plone.app.contenttypes (PyPI): affected from 4.0.0; fixed in 4.0.10
- plone.app.contenttypes (PyPI): affected from 5.0.0; fixed in 5.0.1

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/GHSA-8pcw-h6w9-h46g/ (Markdown: https://insights.sbomify.com/GHSA-8pcw-h6w9-h46g/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-8pcw-h6w9-h46g

---
From sbomify Insights: https://insights.sbomify.com/GHSA-8pcw-h6w9-h46g/
Summaries are generated and may contain mistakes; the official description above is the record.