| CVE | Icon | Vulnerability name | Date | Responsible Security Disclosure by | Stars | Process | Vulnerabilities |
|---|---|---|---|---|---|---|---|
| CVE requested | GroupLinkBleed | 2026-11-06 | bhaswanthc | Reported privately by bhaswanthc through GitHub Security Advisory GHSA-v544-rmr5-38gx, with a proof of concept, a regression test and a suggested fix; validated and fixed by xet7. |
A board admin could write the board document directly over DDP instead of calling the board methods, and so skip their checks: attach an organization or team they do not belong to, so that its members saw the board and became its members, and add any user to the board past the invitation checks, including the administrator's same organization/team policy. |
The board collection's allow rule lets a board admin update any field of their board. Two restrictions existed only inside Meteor methods: a board admin may add only the organizations and teams they belong to (setBoardOrgs, setBoardTeams, issue #5141), and inviteUserToBoard checks who may invite, refuses a disabled account and applies the administrator's "board members from the same organization/team only" policy (#6116). A client that called /boards/update or /boards/insert directly - Boards.update(boardId, { $set: { teams: [...] } }) in the browser console - reached none of those checks. A team attached that way showed the board to all its members in All Boards and made them members when the group's memberships were propagated; a user pushed into members was a member immediately. No data of another board was exposed. Affected v12.97 and earlier.
Fix: new deny rules in server/permissions/boards.js refuse any client insert or update that names orgs, teams or domains - the interface changes them only through the board methods, which write on the server where allow and deny rules do not apply - and any client update that adds a member to members or switches a removed member back on (models/lib/boardWriteGuards.js). Role changes and removals, which the client writes itself, still pass.
A refused write is recorded in Admin Panel / Problems as GroupLinkBleed (keys authz.group-link and authz.member-add). The interface never makes these writes, so only a client bypassing it reaches the refusal. Medium severity: it never disables the account.
tests/groupLinkBleed.test.cjs runs the real deny rules against the reporter's writes and against every write the client legitimately makes, and fails if a board field guarded only by a method is left writable by the client. tests/playwright/specs/group-link-bleed.e2e.js replays the attack over DDP against a running server.