CVE-2026-30953: LinkAce affected by SSRF via link creation: NoPrivateIpRule not applied to LinkStoreRequest
LinkAce is a self-hosted archive to collect website links. When a user creates a link via POST /links, the server fetches HTML metadata from the provided URL (LinkRepository::create() calls HtmlMeta::getFromUrl()). The LinkStoreRequest validation rules do not include NoPrivateIpRule, allowing server-side requests to internal network addresses, Docker service hostnames, and cloud metadata endpoints. The project already has a NoPrivateIpRule class (app/Rules/NoPrivateIpRule.php) but it is only applied in FetchController.php (line 99), not in the primary link creation path.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-30953?
CVE-2026-30953 is considered a medium severity vulnerability due to its potential for SSRF attacks.
How do I fix CVE-2026-30953?
To fix CVE-2026-30953, ensure that the NoPrivateIpRule is properly implemented in your LinkAce instance.
What impact does CVE-2026-30953 have on my LinkAce installation?
CVE-2026-30953 could allow an attacker to access internal resources through a crafted link, risking data exposure.
Is CVE-2026-30953 exploitable remotely?
Yes, CVE-2026-30953 is remotely exploitable as it involves user input in link creation.
Which version of LinkAce is affected by CVE-2026-30953?
All versions of LinkAce that allow link creation without the proper NoPrivateIpRule implementation are affected by CVE-2026-30953.