CVE-2026-47170: Garlic-Hub SSRF Vulnerability – Internal Reconnaissance Risk

Technical summary

CVE-2026-47170 is a Server-Side Request Forgery (SSRF) vulnerability in the uploadFromUrl endpoint of Garlic-Hub prior to version 1.1. The endpoint fails to validate or restrict the target URL, allowing authenticated users to force the server to initiate HTTP connections to arbitrary internal addresses and ports. The server's responses are stored in the media pool without access controls, creating an information disclosure channel. The attack requires valid authentication credentials but no elevated privileges, and succeeds over the network with no user interaction.

Business impact

An authenticated user or compromised account can enumerate your internal network, discover and fingerprint internal services (databases, administration panels, APIs), and exfiltrate HTTP responses without triggering traditional network-based alerts. In a hybrid or cloud environment, this may expose internal service meshes, Kubernetes APIs, or metadata endpoints. The public media pool acts as a persistent staging area for exfiltrated data. The impact is primarily reconnaissance and information leakage; no data modification or denial of service occurs, but the recon footprint supports follow-on attacks against discovered internal services.

Affected systems

Garlic-Hub versions prior to 1.1 are vulnerable. The attack surface is limited to authenticated users, so this risk is elevated in environments with weak access controls, shared credentials, or high user counts. Self-hosted deployments with network access to sensitive internal services (databases, admin consoles, cloud metadata endpoints) face the highest exposure.

Exploitability

Exploitation is straightforward once credentials are obtained. An attacker with valid login credentials can directly call the uploadFromUrl endpoint with an internal IP address or hostname and port number, retrieve service banners or API responses, and review the results from the media pool. No complex attack chain, race conditions, or timing is required. The barrier to entry is authentication; if your organization has permissive user provisioning, account sharing, or credential reuse, the practical risk is elevated.

Remediation

Upgrade Garlic-Hub to version 1.1 or later immediately. Verify the upgrade is complete by confirming the installed version in the administrative interface. Simultaneously, audit your Garlic-Hub user roster and revoke credentials for any accounts no longer in active use. If you cannot upgrade immediately, restrict network access to the Garlic-Hub server to a small, trusted IP range or VPN segment, and monitor authentication logs for suspicious login patterns.

Patch guidance

Garlic-Hub version 1.1 contains the fix. Download and deploy it from the official Garlic-Hub repository or vendor site. Test the upgrade in a non-production environment first to verify compatibility with your content playlists and device configurations. No rollback or configuration changes are required post-upgrade, but a full restart of the service is recommended to ensure all components load the patched code.

Detection guidance

Review Garlic-Hub authentication logs for failed or unusual login attempts, particularly from non-standard IP addresses. Monitor the media pool for unexpected files or recent uploads from internal IP addresses or hostnames (e.g., 192.168.*.*, 10.*.*.*, localhost, kubernetes.default, metadata service endpoints). Enable HTTP request logging on internal services if available to spot requests originating from the Garlic-Hub server. Network-side detection is difficult because the traffic is outbound and legitimate; application-level logging is essential.

Why prioritize this

This vulnerability scores 7.7 CVSS (HIGH severity) due to high confidentiality impact and network-accessible attack surface, but is held below critical by the requirement for prior authentication. However, in practice, patch urgently because information disclosure from internal reconnaissance is a critical precursor to lateral movement and data breach. If your Garlic-Hub instance is internet-facing or accessible to a large user population, move this to the top of your queue. If it is air-gapped or restricted to a small trusted team, you have slightly more time, but upgrade within 30 days.

Risk score, explained

CVSS 3.1 score 7.7 reflects a high-impact confidentiality breach (C:H) with no integrity or availability impact (I:N, A:N), accessible over the network without user interaction but requiring prior authentication (AV:N, AC:L, PR:L, UI:N). The score does not account for the downstream risk of reconnaissance enabling lateral movement; treat this as a facilitator vulnerability whose true business risk depends on your internal network architecture and the sensitivity of internal services.

Frequently asked questions