CVE-2026-104184: Kovah LinkAce · Insecure Direct Object Reference
Affects Kovah LinkAceSource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 2.6.0 soon.
Data as of 20 Nov 2026, 17:44 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.1 |
|---|
- Patch
- Available – fixed in 2.6.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 20 Nov 2026.
What to do
Upgrade Kovah LinkAce to 2.6.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| KovahLinkAce | Affected
| Fixed in
|
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.