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

> Authenticated users without Nova access can modify boolean fields on any resource via the toggle endpoint due to missing authorization checks.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-f5c8-m5vw-rmgq

## What is CVE-2026-42202?

CVE-2026-42202 is a medium-severity missing authorization vulnerability in almirhodzic nova-toggle-5, published on 8 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

nova-toggle-5 enables fliping booleans in the index. Prior to version 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. This issue has been patched in version 1.3.0.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-42202?

2 open source packages ship an affected version, including almirhodzic/nova-toggle-5.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `almirhodzic/nova-toggle-5` | Packagist | All versions | 1.3.0 |
| `almirhodzic/nova-toggle-5` | Packagist | All versions | 1.3.0 |

## How do I fix CVE-2026-42202?

Upgrade almirhodzic/nova-toggle-5 to 1.3.0 or later.

## Is CVE-2026-42202 being exploited?

There is no known exploitation of CVE-2026-42202 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42202 and fix it if it is affected.

What it is: CVE-2026-42202 is a medium-severity missing authorization vulnerability in almirhodzic nova-toggle-5, published on 8 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42202 in the wild and no public exploit code.

Affected packages and fixed versions:
- almirhodzic/nova-toggle-5 (Packagist): affected all versions; fixed in 1.3.0
- almirhodzic/nova-toggle-5 (Packagist): affected all versions; fixed in 1.3.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-42202/ (Markdown: https://insights.sbomify.com/CVE-2026-42202/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42202
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42202
- OSV: https://osv.dev/vulnerability/CVE-2026-42202

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-42202/
Summaries are generated and may contain mistakes; the official description above is the record.