Skip to main content
Menu
CVEs

LinkAce ownership transfer via mass assignment in API link update

CVE-2026-104184Published , updated

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 2.6.0
Who is exposed
Not reported

Summary

LinkAce, a self-hosted link archive from Kovah, has a flaw in its API link update that lets a remote attacker with a low-privilege login transfer a link they are allowed to update. By setting the user_id field, the attacker can move the link into another user's bookmark collection or leave it orphaned from any real account.

Written by a model

Original description

LinkAce is a self-hosted archive to collect website links. Prior to 2.6.0, LinkController::update() in app/Http/Controllers/API/LinkController.php passes $request->all() to the repository update method even though user_id is fillable and is not an allowed field in the validated update request. An authenticated API user who is authorized to update a link can therefore assign an arbitrary or nonexistent user_id, transferring the link into another user's bookmark collection or orphaning it from any real account. The web update controller is unaffected because it passes only validated fields. 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-104184 (LinkAce: Mass Assignment via user_id in API Link Update Allows Ownership Transfer and Content Injection), 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-104184 (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-104184 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-104184 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-p25r-m7hm-2rh2
- https://github.com/Kovah/LinkAce/pull/1125
- https://github.com/Kovah/LinkAce/commit/f71134c2e8f2b92e26eef63494542f877657bb67
- 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-104184
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-104184"}.

Affected versions

cve.now Index

10Pof 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
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 29 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-p25r-m7hm-2rh2
CVE record 1Establishes: The identifier and description.
RecordCVE List · CVE-2026-104184
Other links 3
RepositoryGitHub · Kovah/LinkAce · Pull request #1125
RepositoryGitHub · Kovah/LinkAce · Commit f71134c2
RepositoryGitHub · Kovah/LinkAce · Release v2.6.0

Questions about CVE-2026-104184

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

LinkAce: before 2.6.0.

Source: cve.now feed data

How do I fix CVE-2026-104184?

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.