# CVE-2026-45295: Missing authorization in freescout

> Unauthenticated attackers can enumerate conversation IDs and modify thread read status in FreeScout help desk software.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-qjr9-6v9q-3r72

## What is CVE-2026-45295?

CVE-2026-45295 is a medium-severity missing authorization vulnerability in freescout-help-desk freescout, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. Prior to version 1.8.219, the open tracking endpoint `GET /thread/read/{conversation_id}/{thread_id}` allows unauthenticated attackers to enumerate valid conversation and thread IDs, and modify thread state (`opened_at` timestamp) without any authentication. Version 1.8.219 patches the issue.

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

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


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

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

## Is CVE-2026-45295 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45295 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45295 is a medium-severity missing authorization vulnerability in freescout-help-desk freescout, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45295 exists.

Affected product: freescout-help-desk freescout. 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-45295/ (Markdown: https://insights.sbomify.com/CVE-2026-45295/index.md)
```

## Sources

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

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