Evidence · DiggingBeagle record
Pulse advisory: viewer access to AI assistant approvals
Project advisory on missing approval API authorization and independent final action checks.
- Published
- Nov 13, 2026
- Source role
- primary disclosure
Evidence record
Project advisory on missing approval API authorization and independent final action checks.
Claim-level citations (2)
- supportsA Pulse viewer could change another user's AI approval decision without being an approver: The Pulse Assistant approval listing and approve/deny routes required authentication but not the separate approval authority. A same-organization viewer could inspect pending requests and submit a decision using its own browser session and CSRF proof. The advisory shows that the approval record could be mutated even though some legacy command and final effect paths retained independent checks. A changed approval label is therefore a real integrity fault but is not, by itself, evidence that a privileged OS command executed.
Pulse GHSA-9vxw-m79f-gxxr, exploitation steps and final-action caveats
- supportsA Pulse viewer could change another user's AI approval decision without being an approver: The reported issue depends on a vulnerable Pulse version and an already authenticated viewer. The advisory does not establish exploitation against a real customer, and the final executor restrictions need separate tests. The evidence is bounded by the cited source and test setting. Broader incidence, other environments, and actual production consequences are not established merely by these observations.
Primary disclosure: results, scope and limitations