# CVE-2026-61640: Wallos: SSRF via OIDC Token/UserInfo URL Configuration

> Admins can configure malicious OIDC URLs to trigger Server-Side Request Forgery, allowing access to internal networks or cloud metadata.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-x9x5-gh69-q7cm

## What is CVE-2026-61640?

CVE-2026-61640 is a high-severity server-side request forgery vulnerability in ellite Wallos, published on 31 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Wallos is an open-source, self-hostable personal subscription tracker. Prior to version 4.9.6, Admin-configured OIDC token_url and user_info_url in includes/oidc/handle_oidc_callback.php:18-49 are used directly in curl_init() with zero SSRF filtering. Unlike logo/webhook URLs which have validate_webhook_url_for_ssrf(), OIDC URLs bypass all protections. Admin sets URL to http://169.254.169.254/latest/meta-data/ for cloud metadata access or internal network pivoting. This issue has been patched in version 4.9.6.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-61640 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61640 is a high-severity server-side request forgery vulnerability in ellite Wallos, published on 31 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-61640 in the wild and no public exploit code.

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

## Sources

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

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