nova-toggle-5: Improper authorization on toggle endpoint allowed non-Nova users to modify boolean fields

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

EPSS

• CVE-2026-42202: 0.20% estimated exploitation activity in the next 30 days; percentile 10.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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. Patches 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. Workarounds Users who cannot upgrade…

Published by the source

24 Apr 2026, 16:00 UTC

Last modified by the source

13 May 2026, 13:37 UTC

Source last checked

26 Oct 2026, 14:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f5c8-m5vw-rmgq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-42202

Advisory: nova-toggle-5: Improper authorization on toggle endpoint allowed non-Nova users to modify boolean fields
IDs: CVE-2026-42202, GHSA-f5c8-m5vw-rmgq
Record: https://patchnext.com/advisories/cve-2026-42202 (revision 1, source checked 26 Oct 2026, 14:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: almirhodzic/nova-toggle-5 1.3.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist almirhodzic/nova-toggle-5: affected < 1.3.0; fixed in 1.3.0

## Suggested inspection (read-only)
- Packagist almirhodzic/nova-toggle-5: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on almirhodzic/nova-toggle-5.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f5c8-m5vw-rmgq (GitHub-reviewed advisory GHSA-f5c8-m5vw-rmgq lists affected ranges: Packagist almirhodzic/nova-toggle-5 >=0 <1.3.0)

Commands are suggestions: review each one before running it.