CVE-2026-35516

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. Limited direct impact.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-04-07 16:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-26 21:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 5.0 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-04-07 16:16 UTC

Last modified

2026-10-26 21:10 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-918 · Server-side request forgery

Record status

Analyzed

Affected

• Linkace < 2.5.4

Attack profile CVSS 3.1 · 5.0

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Changed

Confidentiality

Low

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-35516.md and follow it. Check whether this project is affected by CVE-2026-35516. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge