# CVE-2026-26957: Withdrawn Advisory: Libredesk has a SSRF Vulnerability in Webhooks


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 19 Feb 2026
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-wgm6-9rvv-3438, GO-2026-4505

## What is CVE-2026-26957?

CVE-2026-26957 is a vulnerability in github.com/abhinavxd/libredesk, published on 19 Feb 2026. 

### Official description

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: Upon further research, the maintainer determined that the behavior described by the CVE record is intended behavior. Per the GitHub Security Advisory: "Libredesk is a single-tenant, self-hosted application. Configuring outbound webhook URLs requires an admin-only permission that is not granted by default - the operator must explicitly assign it. Anyone holding this permission already has full administrative control over the application, and outbound HTTP to operator-chosen URLs is the documented purpose of the webhook feature. This is working as designed." Notes: none.

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

3 open source packages ship an affected version, including github.com/abhinavxd/libredesk.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/abhinavxd/libredesk` | Go | All versions | 1.0.2-0.20260215211005-727213631ce6 |
| `github.com/abhinavxd/libredesk` | Go | All versions | 1.0.2-0.20260215211005-727213631ce6 |
| `github.com/abhinavxd/libredesk` | Go | All versions | 1.0.2-0.20260215211005-727213631ce6 |

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

Upgrade github.com/abhinavxd/libredesk to 1.0.2-0.20260215211005-727213631ce6 or later.

## Is CVE-2026-26957 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-26957 is a vulnerability in github.com/abhinavxd/libredesk, published on 19 Feb 2026. 
Exploitation: There is no known exploitation of CVE-2026-26957 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/abhinavxd/libredesk (Go): affected all versions; fixed in 1.0.2-0.20260215211005-727213631ce6
- github.com/abhinavxd/libredesk (Go): affected all versions; fixed in 1.0.2-0.20260215211005-727213631ce6
- github.com/abhinavxd/libredesk (Go): affected all versions; fixed in 1.0.2-0.20260215211005-727213631ce6

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

## Sources

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

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