A reproduced finding is sitting in the private advisory channel — posting a pointer here because the 20 that preceded it are all still in triage

We filed a security advisory today: GHSA-h888-fcww-xq25. This issue exists only to point at it.

Why publicly, when the finding itself is private. As of today, gh api repos/dfinity/public-multidex/security-advisories returns 21 advisories, all in triage — and 20 of those predate today's, so ours is not what
makes the count. None has been published or closed. That is a statement about state, not about attention: we
cannot tell from outside whether they have been read. But it does mean we have no signal that the
channel is being monitored, and we would rather make the existence of this advisory visible than
risk it going unnoticed.

What we are not doing here. We are not describing the mechanism, the affected path, the
reproduction or the numbers. They are in the advisory. We assess it at [play: MEDIUM / prod: MEDIUM] — we
rated it three times, the last pass ruled against the previous two, and the advisory opens by showing
that working against your published rubric's own wording rather than against our sense of it.

Three things about it that we think justify the interruption:

1. It is reproduced, not argued — on a seeded local #play replica, with the predictions written
   down before the measurements were taken.
2. It requires no privileged access. The precondition is a state the venue can reach on its own;
   whether an attacker can induce that state is the open question we put to you in the advisory,
   and we do not claim they can.
3. It corrects a clearance of ours. We previously told you, in writing, that this class was
   closed. It was not, and the reason our clearance missed it is in the advisory as its own section.
   That part we would want read first.

If the private channel is not the right route, tell us and we will use whichever is. We are not
attached to the mechanism — we are attached to it being seen and handled before the mechanism becomes
public.

We will publish the mechanism and our own correction once you have fixed it, or once you tell us it
is safe to. The correction arms nobody and is worth more in public than in private.

Pinned to 60f75f6. 585814ef is the only commit after it and contains no code.

Start with security advisory GHSA-h888-fcww-xq25 and the pinned commit 60f75f6; the mechanism, affected path, reproduction, and correction are intentionally omitted from this issue. Review the advisory's section explaining the previous clearance and determine the appropriate handling route. Done means the advisory is handled and the reporter is told whether public disclosure is safe.