Skip to main content
VulnerabilityPublished Updated

CVE-2026-35516: Kovah LinkAce · Server-Side Request Forgery (SSRF)

Affects Kovah LinkAceSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.0 Medium : upgrade to 2.5.4 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
5.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.5.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade LinkAce and kovah/LinkAce to 2.5.4.

Affected software

ProductAffectedFixed in
KovahLinkAceAffected
  • <2.5.4
Fixed in
  • 2.5.4
GitHubkovah/LinkAcepkg:github/kovah/LinkAceOther threatsAffected
  • <2.5.4
Fixed in
  • 2.5.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in LinkAce version 2.5.4 that properly validates and blocks requests to private IP addresses in the vulnerable functions. Since LinkAce is a cloud service, the vendor manages remediation server-side. Users should ensure they are running version 2.5.4 or later. Patch status is confirmed by the vendor advisory. No additional mitigation steps are indicated.

Description

LinkAce is a self-hosted archive to collect website links. Prior to 2.5.4, LinkRepository::update and CheckLinksCommand::checkLink do not check for private IPs. An authenticated user can read responses from internal services (AWS IMDSv1, cloud metadata, internal APIs) by creating a link with a public URL and then updating it to a private IP. The links:check cron job makes the request server-side without IP filtering. This can expose cloud credentials, internal service data, and network topology. This vulnerability is fixed in 2.5.4.

References

Community reviews

Loading reviews…