What is CVE-2025-61668?

CVE-2025-61668 is a high-severity null pointer dereference vulnerability in @plone/volto (npm), affecting versions < 16.34.1. It is fixed in 16.34.1, 17.22.2, 18.27.2, 19.0.0-alpha.6. The application dereferences a null pointer, causing a crash.

Which versions of @plone/volto are affected by CVE-2025-61668?

@plone/volto (npm) versions < 16.34.1 is affected.

Is there a fix for CVE-2025-61668?

Yes. CVE-2025-61668 is fixed in 16.34.1, 17.22.2, 18.27.2, 19.0.0-alpha.6. Upgrade to this version or later.

Is CVE-2025-61668 exploitable, and should I be worried?

Whether CVE-2025-61668 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-61668 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2025-61668?

Upgrade: @plone/volto to 16.34.1 or later, @plone/volto to 17.22.2 or later, @plone/volto to 18.27.2 or later, @plone/volto to 19.0.0-alpha.6 or later.

CVE-2025-61668 in @plone/volto | Intelligent Application Security

Q: Which versions of @plone/volto are affected by CVE-2025-61668?

@plone/volto (npm) versions < 16.34.1 is affected.

Q: Is there a fix for CVE-2025-61668?

Yes. CVE-2025-61668 is fixed in 16.34.1, 17.22.2, 18.27.2, 19.0.0-alpha.6. Upgrade to this version or later.

Q: Is CVE-2025-61668 exploitable, and should I be worried?

Whether CVE-2025-61668 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-61668 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-61668?

Upgrade: @plone/volto to 16.34.1 or later, @plone/volto to 17.22.2 or later, @plone/volto to 18.27.2 or later, @plone/volto to 19.0.0-alpha.6 or later.

Summary

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]).

Impact

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

The application dereferences a null pointer, causing a crash. Typical impact: denial of service via crash.

Affected versions

@plone/volto (< 16.34.1) @plone/volto (>= 17.0.0, < 17.22.2) @plone/volto (>= 18.0.0, < 18.27.2) @plone/volto (>= 19.0.0-alpha.1, < 19.0.0-alpha.6)

Security releases

@plone/volto → 16.34.1 (npm) @plone/volto → 17.22.2 (npm) @plone/volto → 18.27.2 (npm) @plone/volto → 19.0.0-alpha.6 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

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

Frequently Asked Questions

What is CVE-2025-61668? CVE-2025-61668 is a high-severity null pointer dereference vulnerability in @plone/volto (npm), affecting versions < 16.34.1. It is fixed in 16.34.1, 17.22.2, 18.27.2, 19.0.0-alpha.6. The application dereferences a null pointer, causing a crash.
Which versions of @plone/volto are affected by CVE-2025-61668? @plone/volto (npm) versions < 16.34.1 is affected.
Is there a fix for CVE-2025-61668? Yes. CVE-2025-61668 is fixed in 16.34.1, 17.22.2, 18.27.2, 19.0.0-alpha.6. Upgrade to this version or later.
Is CVE-2025-61668 exploitable, and should I be worried? Whether CVE-2025-61668 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-61668 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-61668?
- Upgrade @plone/volto to 16.34.1 or later
- Upgrade @plone/volto to 17.22.2 or later
- Upgrade @plone/volto to 18.27.2 or later
- Upgrade @plone/volto to 19.0.0-alpha.6 or later

Other vulnerabilities in @plone/volto

CVE-2025-61668 CVE-2022-24740