CVE-2026-104186 in LinkAceinfo

Summary

by MITRE • 11/20/2026

LinkAce is a self-hosted archive to collect website links. Prior to 2.6.0, the authenticated GET /lists/{list}/feed and GET /tags/{tag}/feed handlers in app/Http/Controllers/App/FeedController.php use integer route model binding without an object-level authorization or visibility check. Unlike the web list controller, which invokes LinkListPolicy::view(), the feed controller lets a normal authenticated user enumerate another user's private list or tag and receive its name and feed metadata, along with public or internal bookmark entries associated with that taxonomy. The existing per-link visibility filter still excludes PRIVATE link records, so the disclosure is limited to the private taxonomy and its non-private member links. This issue is fixed in version 2.6.0.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 11/20/2026

The vulnerability identified in LinkAce versions prior to 2.6.0 represents a critical failure in object-level authorization within the application's feed handling mechanisms. Specifically, the authenticated endpoints GET /lists/{list}/feed and GET /tags/{tag}/feed located in app/Http/Controllers/App/FeedController.php rely on integer route model binding without implementing any form of access control verification. This architectural oversight allows an attacker who has successfully authenticated to the application to bypass intended privacy restrictions by directly manipulating URL parameters associated with other users' data structures.

In a properly secured implementation, such as that found in the web list controller which correctly invokes LinkListPolicy::view(), the system verifies whether the current user possesses permission to view or interact with the specific resource identified by the route parameter. However, the feed controllers lack this equivalent policy check. Consequently, an authenticated attacker can enumerate arbitrary identifiers for lists and tags belonging to other users. By supplying these identifiers in the request URL, the application processes the query without validating ownership or visibility permissions, leading to a direct information disclosure vulnerability.

The operational impact of this flaw is significant as it enables unauthorized enumeration of private taxonomies within the LinkAce ecosystem. When an attacker accesses these endpoints with another user's list or tag identifier, they receive metadata including the name of the taxonomy and associated feed details. Furthermore, while the application correctly filters out links marked as PRIVATE at the individual record level, it still exposes all non-private bookmark entries linked to that specific private taxonomy. This means that even if a user considers their collection private, any bookmarks within those collections that are not individually flagged as private remain visible to unauthorized users who discover or guess the list or tag identifiers.

This vulnerability aligns with CWE-284 Improper Access Control and CWE-601 URL Redirection to Untrusted Site (in terms of identifier manipulation leading to unintended data access), though it is most accurately categorized under CWE-862 Missing Authorization, as the server fails to enforce authorization policies on a specific resource. From an ATT&CK perspective, this behavior facilitates Discovery techniques, specifically Internal Network Service Scanning or Account Enumeration, allowing adversaries to map out the structure and contents of other users' archives without explicit permission.

To mitigate this vulnerability, organizations running LinkAce must upgrade immediately to version 2.6.0 or later, where the feed controllers have been patched to include proper object-level authorization checks similar to those present in the main web interface. For environments that cannot be upgraded instantly due to operational constraints, temporary mitigations should focus on restricting access to these specific endpoints via network security controls such as Web Application Firewalls (WAFs) or reverse proxy configurations. These controls can validate user permissions before requests reach the application logic, ensuring that only authorized users can interact with feed resources belonging to their own accounts. Additionally, implementing strict input validation and logging for unusual patterns of identifier enumeration can aid in early detection of exploitation attempts while permanent fixes are deployed.

Responsible

GitHub M

Reservation

10/01/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00382

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!