CVE-2026-42202

Workarounds

Users who cannot upgrade immediately can either remove the package or restrict access to the /nova-vendor/nova-toggle/toggle/* routes via an additional middleware in their application that enforces the viewNova gate.

Credits

nova-toggle-5 thanks Roberto Negro for the responsible disclosure.

In versions < 1.3.0, the toggle endpoint (POST /nova-vendor/nova-toggle/toggle/{resource}/{resourceId}) was protected only by web + auth:<guard> middleware. Any user authenticated on the configured guard could call the endpoint and flip boolean attributes on any Nova resource, including users who do not have access to Nova itself (for example, frontend customers sharing the web guard with the Nova admin area).

The endpoint also accepted an arbitrary attribute parameter, which meant a valid caller could toggle any boolean column on the underlying model, not just columns exposed as Toggle fields on the resource.

CVE-2026-42202 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.3.0); upgrading removes the vulnerable code path.

Kodem intelligence

Fixed in 1.3.0:

• The route is now protected by Nova's nova:api middleware, which enforces the viewNova gate.
• The controller now checks the resource's authorizedToUpdate policy.
• The controller only accepts attributes that are declared as a Toggle field on the resource and are not readonly in the current request context.

1. What is CVE-2026-42202? CVE-2026-42202 is a medium-severity security vulnerability in almirhodzic/nova-toggle-5 (composer), affecting versions < 1.3.0. It is fixed in 1.3.0.
2. How severe is CVE-2026-42202? CVE-2026-42202 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of almirhodzic/nova-toggle-5 are affected by CVE-2026-42202? almirhodzic/nova-toggle-5 (composer) versions < 1.3.0 is affected.
4. Is there a fix for CVE-2026-42202? Yes. CVE-2026-42202 is fixed in 1.3.0. Upgrade to this version or later.
5. Is CVE-2026-42202 exploitable, and should I be worried? Whether CVE-2026-42202 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
6. What actually determines whether CVE-2026-42202 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.
7. How do I fix CVE-2026-42202? Upgrade almirhodzic/nova-toggle-5 to 1.3.0 or later.