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

> Unauthenticated attackers can trigger Server-Side Request Forgery in Wallos via the payments search endpoint due to an incomplete security fix.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 31 Aug 2026
- **Updated:** 3 Sep 2026

## What is CVE-2026-77348?

CVE-2026-77348 is a high-severity server-side request forgery vulnerability in ellite Wallos, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Wallos is an open-source, self-hostable personal subscription tracker. Prior to version 5.0.0, the fix for CVE-2026-33407 (GHSA-hhjq-82f8-m6rc, "SSRF via HTTP Proxy Environment Variable") hardened endpoints/logos/search.php by disabling cURL proxying (CURLOPT_PROXY = '' + CURLOPT_NOPROXY = '*'). However, Wallos ships a second, near-identical, unauthenticated logo-image search endpoint — endpoints/payments/search.php — that was not given the same hardening. It still passes the HTTP_PROXY/HTTPS_PROXY environment variable straight into CURLOPT_PROXY. This issue has been patched in version 5.0.0.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-441 (Unintended Proxy or Intermediary), CWE-1188 (Initialization of a Resource with an Insecure Default)

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


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

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

## Is CVE-2026-77348 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77348 is a high-severity server-side request forgery vulnerability in ellite Wallos, published on 31 Aug 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-77348 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-77348/ (Markdown: https://insights.sbomify.com/CVE-2026-77348/index.md)
```

## Sources

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

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