# CVE-2026-123207: LibreTV before v2.21.2 SSRF Protection Bypass via DNS Rebinding


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-55w8-f34c-fr45

## What is CVE-2026-123207?

CVE-2026-123207 is a low-severity vulnerability in LibreSpark LibreTV, published on 5 Nov 2026. 

### Official description

LibreTV before v2.21.2 contains a server-side request forgery vulnerability that allows authenticated users to bypass checkUpstreamAllowed() by exploiting unpinned DNS resolution in fetchWithSafeRedirects(). Attackers controlling authoritative DNS can return public addresses during validation and internal addresses at connection time via /api/source/test, /api/proxy, /api/search or /api/detail to reach loopback services, private hosts or cloud metadata endpoints.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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


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

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

## Is CVE-2026-123207 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123207 is a low-severity vulnerability in LibreSpark LibreTV, published on 5 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123207 in the wild and no public exploit code.

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

## Sources

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

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