CVE-2026-33953: LinkAce's SSRF protection can be bypassed via internal hostname resolution in LinkAce
LinkAce is a self-hosted archive to collect website links. Versions prior to 2.5.3 block direct requests to private IP literals, but still performs server-side requests to internal-only resources when those resources are referenced through an internal hostname. This allows an authenticated user to trigger server-side requests to internal services reachable by the LinkAce server but not directly reachable by an external user. Version 2.5.3 patches the issue.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-33953?
CVE-2026-33953 is considered a high-severity vulnerability due to its potential impact on information leakage through SSRF.
How do I fix CVE-2026-33953?
To fix CVE-2026-33953, upgrade to LinkAce version 2.5.3 or later where the vulnerability has been patched.
What does CVE-2026-33953 affect?
CVE-2026-33953 affects LinkAce versions prior to 2.5.3, specifically targeting its SSRF protection.
What is SSRF and how is it related to CVE-2026-33953?
SSRF stands for Server-Side Request Forgery, and CVE-2026-33953 allows attackers to bypass SSRF protection in LinkAce.
Can I check if my LinkAce version is vulnerable to CVE-2026-33953?
You can check if your LinkAce version is vulnerable to CVE-2026-33953 by verifying if it is below version 2.5.3.