PULSE
FEED
ransomaurora reclama a TraWell Co S.p.A. (d/b/a Safe Bag) · IT · Retail & E-Commerceransomeverstake reclama a al*****o.comransomrhysida reclama a Clarkesville Police Department, City of Clarkesville · GA · Government & Defenseransomaurora 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 · Otherransomaurora reclama a TraWell Co S.p.A. (d/b/a Safe Bag) · IT · Retail & E-Commerceransomeverstake reclama a al*****o.comransomrhysida reclama a Clarkesville Police Department, City of Clarkesville · GA · Government & Defenseransomaurora 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 · Other
← Todos os CVEs
CVE Watch19 de nov. de 2026

CVE-2026-113458

Mattermost versions 11.10.x <= 11.10.2, 11.11.x <= 11.11.1, 11.7.x <= 11.7.12 fail to validate the format of configured database connection

CVSS

4.5

Média

EPSS

—

KEV

—

Exploit Today

0

0-100

Publicado: 19 de nov. de 2026 · Última mod.: 19 de nov. de 2026 · CWE-200

EPSS · 30d

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

Descrição técnica

Mattermost versions 11.10.x <= 11.10.2, 11.11.x <= 11.11.1, 11.7.x <= 11.7.12 fail to validate the format of configured database connection strings before redacting them, which allows a party with access to a generated Support Packet or server log files to recover plaintext database credentials when the connection string is configured in a non-URL format.. Mattermost Advisory ID: MMSA-2026-00783

Referências oficiais
CVEs relacionados
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-77390—
—
———pmo-platform is a modular PMO and release-management platform for Claude Code. Prior to 3.73, release/skills/pmo-skill-refiner/eval-viewer/generate_review.py and viewer.html contain three security weaknesses in the local evaluation viewer. During workspace scanning and generation, _find_runs_recursive and build_run follow symlinks and embed_file reads their targets without confining resolved paths to the workspace, although the server do_GET path is not a traversal surface. embed_file also reads output files without a size cap or redaction, allowing secrets or personally identifiable information to be embedded in a no-auth locally served page or shareable static file. Separately, do_POST /api/feedback writes caller-supplied JSON without authentication, an Origin check, or a cross-site request forgery token, allowing a malicious page or DNS-rebound localhost target to modify feedback while the server runs. This issue is fixed in version 3.73.2h
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.2h
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.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.3h
CVE-2026-133853—
—
———FlowIntel's chatbot component used a single shared MCP (Model Context Protocol) session and process-wide environment variable to pass per-user API credentials to a child process. Because the session and the ambient FLOWINTEL_API_KEY environment variable were shared across all concurrent requests, a user's authenticated identity could be applied to another user's tool invocation, or a stale/ambient credential could be inherited by a new request. Preconditions: - An authenticated user with access to the chatbot interface. - Concurrent or overlapping chatbot tool invocations from different users, or a request made after another user's credentials were written to the process environment. Impact: - A lower-privilege user could read data belonging to a higher-privilege user (e.g., private investigation cases). - A user whose session was invalidated (deleted, password changed, key revoked) could still operate under a previously cached ambient credential. - The parent process environment was mutated with user-specific secrets, creating a persistent credential leak surface. Affected versions: FlowIntel prior to 4.1.0.3h
CVE-2026-133841—
—
———FlowIntel contains an authorization bypass in its case serialization logic that allows an authenticated user to view metadata of private cases they do not have access to. When a case is linked to another case, the JSON representation of the source case included the ID, title, and description of every linked case regardless of the requesting user's permissions. This affected multiple access paths: - Browser views (case detail, case info, search, calendar) - REST API endpoints (get case, list cases, search, title lookup, completed/not-completed lists) - Internal tooling and connector module context building An attacker with valid credentials and access to any case that contains a link to a private case could enumerate the private case's identifier, title, and description without holding a membership or role on that private case. The exposure occurred because the serialization method did not receive or evaluate the acting user's identity before including linked-case data in the response. Security impact: - Disclosure of private case identifiers, titles, and descriptions to unauthorized users - Facilitation of further targeted attacks against the exposed private cases - Bypass of the intended per-case access control model Affected versions: FlowIntel prior to 4.1.03h