Skip to main content
Menu
CVEs

LinkAce private link existence leak in HTML bookmark import

CVE-2026-104185Published , updated

4.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2.6.0
Who is exposed
Not reported

Summary

LinkAce, a self-hosted link archive, has a flaw in its HTML bookmark import that lets a logged-in user check whether any account has saved a chosen URL, including as a private bookmark. The attack can be carried out remotely by any user with a basic login, and it reveals only whether the URL exists, not the bookmark contents or its owner.

Written by a model

Original description

LinkAce is a self-hosted archive to collect website links. Prior to 2.6.0, the HTML bookmark import action in app/Actions/ImportHtmlBookmarks.php uses the global Link::whereUrl() lookup instead of restricting duplicate detection to the importing user. An authenticated user can submit a chosen URL and distinguish the skipped response count from the queued count to learn whether any account has saved that URL, including as a PRIVATE bookmark. The oracle reveals URL existence but does not directly return the bookmark contents or owner. This issue is fixed in version 2.6.0.

What to do

Upgrade to a fixed version: 2.6.0.

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-104185 (LinkAce: Private Bookmark URL Existence Oracle via HTML Import Skipped-Count Leaks 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-104185 (entry last updated 2026-11-20):
Affected:
- Kovah LinkAce: fixed in 2.6.0
Fixed versions: 2.6.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-104185 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-104185 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-m2vw-5qrg-6x57
- https://github.com/Kovah/LinkAce/pull/1125
- https://github.com/Kovah/LinkAce/commit/dd3e24bad8ee258f2ca040187442b07dcbd4a9d1
- https://github.com/Kovah/LinkAce/releases/tag/v2.6.0
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-104185
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-104185"}.

Affected versions

cve.now Index

7Pof 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
  • Severity4.3/10CVSS 4.3
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 26 if advisories confirm default setups are exposed

Timeline

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

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · Kovah/LinkAce · Advisory GHSA-m2vw-5qrg-6x57
CVE record 1Establishes: The identifier and description.
RecordCVE List · CVE-2026-104185
Other links 3
RepositoryGitHub · Kovah/LinkAce · Pull request #1125
RepositoryGitHub · Kovah/LinkAce · Commit dd3e24ba
RepositoryGitHub · Kovah/LinkAce · Release v2.6.0

Questions about CVE-2026-104185

Is CVE-2026-104185 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-104185?

LinkAce: before 2.6.0.

Source: cve.now feed data

How do I fix CVE-2026-104185?

Upgrade to a fixed version: 2.6.0.

Source: cve.now feed data

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