# CVE-2026-41192: FreeScout's client-controlled attachment IDs allow deletion of existing conversation attachments


- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Apr 2026
- **Updated:** 21 Apr 2026
- **Also known as:** GHSA-cv36-2j23-x6g3

## What is CVE-2026-41192?

CVE-2026-41192 is a high-severity vulnerability in freescout-help-desk freescout, published on 21 Apr 2026. 

### Official description

FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.215, the reply and draft flows trust client-supplied encrypted attachment IDs. Any IDs present in `attachments_all[]` but omitted from retained lists are decrypted and passed directly to `Attachment::deleteByIds()`. Because `load_attachments` returns encrypted IDs for attachments on a visible conversation, a mailbox peer can replay those IDs through `save_draft` and delete the original attachment row and file. Version 1.8.215 fixes the vulnerability.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-41192 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41192 is a high-severity vulnerability in freescout-help-desk freescout, published on 21 Apr 2026. 
Exploitation: There is no known exploitation of CVE-2026-41192 in the wild and no public exploit code.

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

## Sources

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

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