Repository navigation
Description
Security Finding
Severity: high (finding 1), medium (findings 2 to 4)
Type: unsafe-pattern / permission-issue — details withheld
Risk: security
The sec-check lane audited main at d6b8d54 on 2026-11-17 and has four findings in one area that SECURITY.md lists under "What to report" ("Extension privilege escalation"). SECURITY.md says not to open a public issue for a vulnerability, so this issue names the component and nothing else.
Component: the extension host API, which is the set of calls the engine serves for an extension worker (crates/compass-worker-host and the extension_* modules of crates/compass). An installed extension can act outside the boundary that the "Security model" section describes, without a kernel exploit. The findings apply to the Flatpak and to the other packages, and to the releases v0.28.2 to v0.28.4.
This is not the report behind #363. That one covers the kernel boundary and the keyboard helper. These four are separate code paths and need their own fixes.
All four were found by reading the code. None was run against a built Compass, because this lane has no Rust toolchain. The report says, claim by claim, what was read and what is only expected.
Where the report is
The lane followed the ruling on #363: the full report (affected lines, reasoning, a proposed fix and the tests that fail today, per finding) is in the lane's private reports directory on the Hive host. The file name is:
compass-extension-host-api-outside-sandbox.md
No pull request comes with this issue. A public fix would describe the problem. None of the fixes needs a workflow, a secret or a setting.
Impact
Finding 1 affects anyone who installs an extension from either store: the sandbox is the reason an untrusted extension is acceptable. Findings 2 and 4 depend on what else is installed. Finding 3 affects KDE Plasma sessions only.
Recommendation
Option A: Keep it private, as on #363. File the report as a private draft security advisory on this repository and land the fixes from the advisory's private fork. Reply /hive done when the report is filed.
Option B: Publish. The lane posts the four findings in this issue and the hive opens the fixes as ordinary public pull requests.
Option C: Add the report to the advisory that already exists for #363, and fix both there.
Recommended: A, because it is the route SECURITY.md promises and the one already chosen on #363, and the four fixes are independent of the fix in that advisory.
Done when
- the report has reached an owner by a private route, or an owner has asked for it to be posted here
- each of the four findings has its own fix or a recorded decision not to fix
Filed by sec-check agent (ACMM L6 — full mode)
🐝 Hive Agent: security | Instance: reef | SHA: 2ef7dc7c08731aef8e67ec0a18309101ceceb430
— hive: agent=sec-check backend=claude model=claude-fable-5-2 effort=high claude=2.1.322
Activity
tuna-reef-hive commentedon Nov 17, 2026
Tip
What to reply
/hive approve→ go with the recommendation (option A): Keep it private, as on [sec-check] Two findings in the extension sandbox and the keyboard helper (details withheld per SECURITY.md) #363. File the report as a private draft security advisory on this repository and land the fixes from the advisory's private fork. Repl … (recommended)/hive decision B→ go with option B: Publish. The lane posts the four findings in this issue and the hive opens the fixes as ordinary public pull requests./hive decision C→ go with option C: Add the report to the advisory that already exists for [sec-check] Two findings in the extension sandbox and the keyboard helper (details withheld per SECURITY.md) #363, and fix both there./hive help→ show these againIf what this issue waited on has been done (a merged fix, or an action taken outside this repository), a maintainer can reply
/fixedto close it as completed; Hive clears its park labels.Only a maintainer with write access can un-park; everything else is ignored. Full command reference: https://github.com/hivecommons/hive/blob/v5/src/docs/maintainer-commands.md.
hanthor commentedon Nov 17, 2026
/hive done
Filed privately as a draft security advisory. The fixes will land from its private fork.
tuna-reef-hive commentedon Nov 17, 2026
Un-parked by @hanthor. Decision: the owner-only step is done; Hive re-checks it and closes the issue once the fix is verified
stage/045-needs-decisionremoved andapproved-directionis applied; anyholdlabel is left exactly as it was.tuna-reef-hive commentedon Nov 19, 2026
Re-checked, and the fix holds. Closing.
The four findings behind this issue are fixed by #373 (v0.28.5). I read each of the four changes and its tests on
mainat 5b5787b.The re-check also found things next to them that #373 does not cover. Those are a new report, not part of this one. #363 tracks it, and the details stay private there as before.
sec-check agent (ACMM L6 — full mode)
— hive: agent=sec-check backend=claude model=claude-fable-5-2 effort=high claude=2.1.322