PULSE
FEED
ransomaurora reclama a William Cook Holdings Limited · GB · Manufacturingransomakira reclama a Pecora · IT · Otherransombarracuda reclama a Dallas Theological Seminary · US · Educationransomblackout reclama a wakao.co.jp · JP · Otherransomincransom reclama a eni.it · IT · Energy & Utilitiesransomspacebears reclama a Inlandboatmen’s Union of the Pacific — Marine Division of the ILWU · US · Transportationransomspacebears reclama a SDJ Design Engineering Limited · GB · Manufacturingransomspacebears reclama a Rise | A Community Service Partnership (also known as NJ Rise) · US · Otherransomspacebears reclama a Epoch Residential · US · Hospitalityransomincransom reclama a Boeing · US · Government & Defenseransomhandsome boy hacking club reclama a FIFA (Fédération Internationale de Football Association) · CH · Otherransomrhysida reclama a Rudolph F. Jass, Jr., PLLC · US · Professional Servicesransomsilentransomgroup reclama a J... W...ransominception reclama a AutoZone, Inc. · US · Retail & E-Commerceransomaurora reclama a William Cook Holdings Limited · GB · Manufacturingransomakira reclama a Pecora · IT · Otherransombarracuda reclama a Dallas Theological Seminary · US · Educationransomblackout reclama a wakao.co.jp · JP · Otherransomincransom reclama a eni.it · IT · Energy & Utilitiesransomspacebears reclama a Inlandboatmen’s Union of the Pacific — Marine Division of the ILWU · US · Transportationransomspacebears reclama a SDJ Design Engineering Limited · GB · Manufacturingransomspacebears reclama a Rise | A Community Service Partnership (also known as NJ Rise) · US · Otherransomspacebears reclama a Epoch Residential · US · Hospitalityransomincransom reclama a Boeing · US · Government & Defenseransomhandsome boy hacking club reclama a FIFA (Fédération Internationale de Football Association) · CH · Otherransomrhysida reclama a Rudolph F. Jass, Jr., PLLC · US · Professional Servicesransomsilentransomgroup reclama a J... W...ransominception reclama a AutoZone, Inc. · US · Retail & E-Commerce
← Todos os CVEs
CVE Watch20 de nov. de 2026

CVE-2026-104186

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

CVSS

4.3

Média

EPSS

—

KEV

—

Exploit Today

—

0-100

Publicado: 20 de nov. de 2026 · Última mod.: 20 de nov. de 2026 · CWE-639 · CWE-862

EPSS · 30d

Ainda não há histórico EPSS suficiente.

Descrição técnica

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.

Referências oficiais
CVEs relacionados
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-59968—
—
———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.41m
CVE-2026-1041854.3 MÉD
—
———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.41m
CVE-2026-1041847.1 ALT
—
———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.41m
CVE-2026-797517.6 ALT
—
———SportEase is a web application for managing school sports events, class rosters, and competition teams. Prior to 1.3, an authenticated account with is_profile_complete=false can submit an attacker-selected class_id for any class in the currently active event to PUT /api/user/profile during first profile completion. AuthHandler.UpdateProfile accepts the class without validating the user's legitimate membership and automatically derives and assigns the corresponding {class_name}_rep role while isFirstCompletion is true. The attacker can become representative of one selected class, view roster information including email addresses, and add or remove competition-team assignments. Downstream handlers correctly reject access to other classes, so the impact is bounded to the selected class, but the representative privilege cannot be revoked through the exposed API and requires direct database intervention or another out-of-band remediation method. This issue is fixed in version 1.3.2h
CVE-2026-133855—
—
———flowintel contains an information disclosure vulnerability in its case history feature. When a user views the history of a case they are authorized to access, the history output includes references to other cases (linked, unlinked, or forked) without verifying whether the requesting user has permission to view those referenced cases. This exposes the identifiers and titles of cases that the user should not be able to discover. The vulnerability affects multiple output paths: - Browser-based case history view - API history endpoint - Plain-text history download - Markdown history download - Report timeline generation An authenticated user with access to any single case can enumerate the existence and identifiers of other cases by reading the history of a case they can access. This bypasses the intended per-case access control model and may reveal the existence of sensitive investigations, their identifiers, and associated metadata to unauthorized users. The raw audit storage is not modified; the issue is solely in the presentation layer failing to filter references to inaccessible cases before returning history data to the user. Affected versions: flowintel prior to 4.1.0.2h
CVE-2026-133854—
—
———flowintel contains a vulnerability in the case and task classification usage endpoints that allows authenticated users to view classification data associated with cases they do not have permission to access. The affected endpoints, which provide lists of used taxonomies, tags, galaxies, clusters, and custom tags, did not properly enforce object-level access controls. While the endpoints required authentication, they failed to filter the returned data based on the requesting user's visibility permissions for the underlying cases. This allowed any authenticated user to enumerate classification usage across all cases, including private or restricted cases belonging to other organizations or users. This issue could lead to the disclosure of sensitive information, such as the existence of specific cases, the types of threats or indicators associated with them, and the relationships between different classification elements, potentially aiding an attacker in reconnaissance or targeting. Affected versions: < 4.1.02h