Skip to main content
Menu
CVEs

LinkAce information disclosure in list links API

CVE-2026-59968Published , updated

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2.5.9
Who is exposed
Not reported

Summary

LinkAce, a self-hosted archive for collecting website links, has a flaw in the API endpoint that lists a list's links, which skips the per-link privacy check. A remote attacker with a low-privilege login who can view a shared list can read other users' private links, including their URLs, titles, descriptions, icons, and timestamps, without any user interaction.

Written by a model

Original description

LinkAce is a self-hosted archive to collect website links. Prior to 2.5.9, the authenticated GET /api/v2/lists/{list}/links endpoint in app/Http/Controllers/API/ListLinksController.php authorizes access only to the parent list and then returns its links without applying visibleForUser(). Because another user's INTERNAL or PUBLIC list may legitimately contain PRIVATE links, a normal authenticated user who may view the list can also receive those private link records, including their URLs, titles, descriptions, icons, and timestamps. Equivalent web, tag, notes, and feed handlers apply the per-link visibility scope, so this API handler is the affected exception. This issue is fixed in version 2.5.9.

What to do

Upgrade to a fixed version: 2.5.9.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-59968 (LinkAce: Authenticated visibility-authorization bypass in GET /api/v2/lists/{list}/links discloses other users' private links), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-59968 (entry last updated 2026-11-20):
Affected:
- Kovah LinkAce: fixed in 2.5.9
Fixed versions: 2.5.9.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-59968 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-59968 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Kovah/LinkAce/security/advisories/GHSA-568c-jrfp-ffjg
- https://github.com/Kovah/LinkAce/commit/e8fede2e790f93f5c334a993ae300e9d560ea728
- https://github.com/Kovah/LinkAce/releases/tag/v2.5.9
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-59968
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-59968"}.

Affected versions

cve.now Index

8Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · Kovah/LinkAce · Advisory GHSA-568c-jrfp-ffjg
CVE record 1Establishes: The identifier and description.
RecordCVE List · CVE-2026-59968
Other links 2
RepositoryGitHub · Kovah/LinkAce · Commit e8fede2e
RepositoryGitHub · Kovah/LinkAce · Release v2.5.9

Questions about CVE-2026-59968

Is CVE-2026-59968 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-59968?

LinkAce: before 2.5.9.

Source: cve.now feed data

How do I fix CVE-2026-59968?

Upgrade to a fixed version: 2.5.9.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.