CVE-2026-40348 json
Movary has Authenticated SSRF via Jellyfin Server URL Verification that Allows Internal Network Probing
published 6mo ago modified 14d ago also EUVD-2026-23617
- cvss
- 7.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
Movary is a self hosted web app to track and rate a user's watched movies. Prior to version 0.71.1, an ordinary authenticated user can trigger server-side requests to arbitrary internal targets through `POST /settings/jellyfin/server-url-verify`. The endpoint accepts a user-controlled URL, appends `/system/info/public`, and sends a server-side HTTP request with Guzzle. Because there is no restriction on internal hosts, loopback addresses, or private network ranges, this can be abused for SSRF and internal network probing. Any ordinary authenticated user can use this endpoint to make the server connect to arbitrary internal targets and distinguish between different network states. This enables SSRF-based internal reconnaissance, including host discovery, port-state probing, and service fingerprinting. In certain deployments, it may also be usable to reach internal administrative services or cloud metadata endpoints that are not directly accessible from the outside. Version 0.71.1 fixes the issue.
Patch / fix
- leepeuker movary 0.71.1
- github.com/leepeuker/movary@d459b35 commit
- github.com/leepeuker/movary#751 pull request
- github.com/leepeuker/movary/releases/tag/0.71.1 release
Is CVE-2026-40348 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6mo ago
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/leepeuker/movary/security/advisories/GHSA-2m2v-v563-qqvj referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
Affected products
- leepeuker movary
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/leepeuker/movary/pull/751
issue-tracking, patch
-
github.com
/leepeuker/movary/commit/d459b3513293d41254f7093aef07010a8e5dcf04
patch
-
github.com
/leepeuker/movary/security/advisories/GHSA-2m2v-v563-qqvj
exploit, vendor-advisory
-
github.com
/leepeuker/movary/releases/tag/0.71.1
release-notes
Sources
- CVE List CVE-2026-40348
- NVD CVE-2026-40348
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.