# CVE-2026-111676: Faveo Helpdesk through 2.0.3 Broken Access Control via /ticket/tooltip Endpoint

> Authenticated agents can read tickets from other departments by enumerating IDs, exposing customer data and internal notes.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA: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:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-8f6x-fr2m-f6wc

## What is CVE-2026-111676?

CVE-2026-111676 is a medium-severity missing authorization vulnerability in faveosuite faveo-helpdesk, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Faveo Helpdesk through 2.0.3 contains a broken access control vulnerability that allows authenticated agents to read tickets in other departments via the getTooltip handler. Attackers can enumerate sequential ticketid values on GET /ticket/tooltip to read ticket conversations, including customer personal data and internal agent notes.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-111676 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111676 is a medium-severity missing authorization vulnerability in faveosuite faveo-helpdesk, published on 16 Oct 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-111676 in the wild and no public exploit code.

Affected product: faveosuite faveo-helpdesk. 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-111676/ (Markdown: https://insights.sbomify.com/CVE-2026-111676/index.md)
```

## Sources

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

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