# CVE-2026-72595: BadChoice Handesk - Broken Access Control

> Authenticated agents can modify tickets belonging to other teams due to missing authorization checks in the update endpoint.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-fwxx-9hp7-v2fg

## What is CVE-2026-72595?

CVE-2026-72595 is a high-severity missing authorization vulnerability in BadChoice Handesk, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A broken access control vulnerability in BadChoice Handesk as of 2026-07-10 allows any authenticated agent to update ticket records belonging to other teams via the TicketsController@update endpoint. The endpoint calls no authorize() method and performs no team-scoped ownership check. An attacker with any agent account can modify, escalate, or corrupt tickets assigned to other teams.

Weakness: CWE-284 (Improper Access Control)

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


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

No fix has been published for CVE-2026-72595 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-72595 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72595 is a high-severity missing authorization vulnerability in BadChoice Handesk, published on 11 Aug 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-72595 in the wild and no public exploit code.

Affected product: BadChoice Handesk. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-72595/ (Markdown: https://insights.sbomify.com/CVE-2026-72595/index.md)
```

## Sources

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

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