How severe is CVE-2025-61668?

No CVSS score has been assigned to CVE-2025-61668 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-61668?

CVE-2025-61668 affects the following packages: @plone/volto (npm), @plone/volto (npm), @plone/volto (npm), @plone/volto (npm). Ecosystems affected: npm.

How do I fix CVE-2025-61668?

Update @plone/volto to 16.34.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-61668 is resolved across your whole dependency graph.

How do I detect CVE-2025-61668 in my npm dependencies?

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-61668 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-61668 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-2025-61668?

CVE-2025-61668 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 38th 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-2025-61668?

CVE-2025-61668 is classified as NULL Pointer Dereference (CWE-476), CWE-754 (CWE-754). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-61668 published, and has it been updated?

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

📦 npm

Not in CISA KEV

CVE-2025-61668 — @plone/volto

Fix: plone/volto@58d9f82

CVE-2025-61668 is a NULL Pointer Dereference vulnerability in @plone/volto. A fix is available for @plone/volto — see the affected versions and patch details below.

@plone/volto vulnerable to potential DoS by invoking specific URL by anonymous user

Also known asGHSA-m8rj-ppph-mj33

Published

Oct 2, 2025

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
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-2025-61668.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

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

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

4other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@plone/voltonpm

4Kdownloads / week

Description

Impact

When visiting a specific URL, an anonymous user could cause the NodeJS server part of Volto to quit with an error.

Patches

The problem has been patched and the patch has been backported to Volto major versions down until 16. It is advised to upgrade to the latest patch release of your respective current major version:

Volto 16: 16.34.1
Volto 17: 17.22.2
Volto 18: 18.27.2
Volto 19: 19.0.0-alpha6

Workarounds

Make sure your setup automatically restarts processes that quit with an error. This won't prevent a crash, but it minimises downtime.

Report

The problem was discovered by FHNW, a client of Plone provider kitconcept, who shared it with the Plone Zope Security Team ([email protected]).

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@plone/volto`	all versions	16.34.1`npm install @plone/volto@16.34.1`
📦npm	`@plone/volto`	≥ 17.0.0&&< 17.22.2	17.22.2`npm install @plone/volto@17.22.2`
📦npm	`@plone/volto`	≥ 18.0.0&&< 18.27.2	18.27.2`npm install @plone/volto@18.27.2`
📦npm	`@plone/volto`	≥ 19.0.0-alpha.1&&< 19.0.0-alpha.6	19.0.0-alpha.6`npm install @plone/volto@19.0.0-alpha.6`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @plone/volto, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @plone/volto to 16.34.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-61668 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact When visiting a specific URL, an anonymous user could cause the NodeJS server part of Volto to quit with an error. ### Patches The problem has been patched and the patch has been backported to Volto major versions down until 16. It is advised to upgrade to the latest patch release of your respective current major version: - Volto 16: [16.34.1](https://github.com/plone/volto/releases/tag/16.34.1) - Volto 17: [17.22.2](https://github.com/plone/volto/releases/tag/17.22.2) - Volto 18: [18.27.2](https://github.com/plone/volto/releases/tag/18.27.2) - Volto 19: [19.0.0-alpha6](https://gi

O3 Security · Impact-Aware SCA

Is CVE-2025-61668 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works