How severe is CVE-2026-57576?

CVE-2026-57576 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2026-57576?

CVE-2026-57576 affects the following packages: plone-app-dexterity (PyPI), plone-app-dexterity (PyPI), plone-app-dexterity (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-57576?

Update plone-app-dexterity to 5.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-57576 is resolved across your whole dependency graph.

How do I detect CVE-2026-57576 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for plone-app-dexterity, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-57576 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2026-57576 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-57576 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-57576?

CVE-2026-57576 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 55th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-57576?

CVE-2026-57576 is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-57576 published, and has it been updated?

CVE-2026-57576 was published on September 22, 2026 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2026-57576 — plone-app-dexterity

MEDIUMFix: plone/plone.app.contenttypes@13dc98a

CVE-2026-57576 is a medium-severity (CVSS 6.5) Uncontrolled Resource Consumption vulnerability in plone-app-dexterity. A fix is available for plone-app-dexterity — see the affected versions and patch details below.

plone.app.dexterity and plone.app.contenttypes have a Denial of Service due to excessive title or description length

Also known asGHSA-5426-92w4-wvhvPYSEC-2026-4137

Published

Sep 22, 2026

Updated

Oct 20, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-57576.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-57576 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,415 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected

🐍plone-app-dexterity🐍plone-app-dexterity🐍plone-app-dexterity

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

When creating content with a very large title or description field, 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.dexterity.

On Plone 6.2, upgrade to plone.app.dexterity 5.0.1.
On Plone 6.1, upgrade to plone.app.dexterity 4.1.3.
On Plone 6.0, upgrade to plone.app.dexterity 3.2.3.

Another part of this problem has been patched in plone.app.contenttypes. See this advisory.

Workarounds

There are no known workarounds.

This problem was responsibly reported by Aldin Visnjic to the Plone/Zope Security Team. 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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`plone-app-dexterity`	≥ 5.0.0&&< 5.0.1	5.0.1`pip install --upgrade 'plone-app-dexterity==5.0.1'`
🐍PyPI	`plone-app-dexterity`	≥ 4.0.0&&< 4.1.3	4.1.3`pip install --upgrade 'plone-app-dexterity==4.1.3'`
🐍PyPI	`plone-app-dexterity`	all versions	3.2.3`pip install --upgrade 'plone-app-dexterity==3.2.3'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for plone-app-dexterity, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update plone-app-dexterity to 5.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-57576 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### Impact When creating content with a very large title or description field, 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.dexterity`. * On Plone 6.2, upgrade to `plone.app.dexterity` 5.0.1. * On Plone 6.1, upgrade to `plone.app.dexterity` 4.1.3. * On Plone 6.0, upgrade to `plone.app.dexterity` 3.2.3. Another part of this problem has been patched in `plone.app.contenttypes`. See [this advisory](https://github.com/plone/plone.app.contenttypes/security/advisories/