# CVE-2026-41689: Server-side request forgery in Wallos

> Low-privilege users can exploit shared webhook allowlists to send arbitrary requests to internal services, potentially leading to remote code execution.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **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:** 7 May 2026
- **Updated:** 7 May 2026
- **Also known as:** GHSA-jx6w-832g-42wv

## What is CVE-2026-41689?

CVE-2026-41689 is a medium-severity server-side request forgery vulnerability in ellite Wallos, published on 7 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Wallos is an open-source, self-hostable personal subscription tracker. In versions 4.8.4 and prior, the webhook notification feature reuses an administrator-configured local-target allowlist for every logged-in user. Any normal user can fully control a webhook URL, headers, and body, then use Wallos to send server-side requests to allowlisted internal automation services. When such a target exposes deployment or execution APIs, this can further enable adjacent-service RCE, but that downstream result is conditional on the target service. At time of publication, there are no publicly available patches.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-41689 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41689 is a medium-severity server-side request forgery vulnerability in ellite Wallos, published on 7 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41689 exists.

Affected product: ellite Wallos. 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-41689/ (Markdown: https://insights.sbomify.com/CVE-2026-41689/index.md)
```

## Sources

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

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