Authenticated SSRF via unrestricted Jellyfin URL verification
Published Apr 18, 2026 · Updated Apr 18, 2026
SSRF in Movary before 0.71.1 allows remote authenticated users to probe internal services through Jellyfin URL verification. The endpoint appends /system/info/public to an untrusted base URL and passes it to Guzzle without blocking loopback, private, or internal DNS targets. Any ordinary account can distinguish reachable services, missing resources, and closed ports through response differences, enabling internal host, port, and service discovery.
Summary
What happened
SSRF in Movary before 0.71.1 allows remote authenticated users to probe internal services through Jellyfin URL verification. The endpoint appends /system/info/public to an untrusted base URL and passes it to Guzzle without blocking loopback, private, or internal DNS targets. Any ordinary account can distinguish reachable services, missing resources, and closed ports through response differences, enabling internal host, port, and service discovery.
The record
- CVE
- CVE-2026-40348
- Published
- Apr 18, 2026
- Updated
- Apr 18, 2026
- Vendor
- Lee Peuker
- Product
- Movary
- Classifications
- CWE-918, T1046
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 18, 2026CVE publishedPublication date reported by the CVE source.
- Apr 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.71.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GitHub advisory SSRF proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo