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…
Inspect the ClaimsCase · DiggingBeagle record
A 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.
Public disclosure: Nov 13, 2026
A viewer session can reach the AI approval API in the affected monitoring management application.
At a glance
The authorization boundary for approval ownership is missing from a route that records another principal's consent.
Read the implicationsThe 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.
Limits and uncertaintyFull account
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.
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.
Mechanism and trust boundary
- 01
Starting condition
A viewer session can reach the AI approval API in the affected monitoring management application.
Boundary: precondition and attacker capability
- 02
Trust boundary crossed or evaluated
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.
Boundary: mechanism
- 03
Observed consequence
The authorization boundary for approval ownership is missing from a route that records another principal's consent.
Boundary: observed effect and limitations
Claims & evidence
CLM-NOV15-PULSEAPPROVAL-MECHThe 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.supported
Basis: reported finding
- supportsPulse advisory: viewer access to AI assistant approvalsprimary disclosure
Pulse GHSA-9vxw-m79f-gxxr, exploitation steps and final-action caveats
CLM-NOV15-PULSEAPPROVAL-SCOPEThe 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.supported
Basis: reported finding
- supportsPulse advisory: viewer access to AI assistant approvalsprimary disclosure
Primary disclosure: results, scope and limitations
Implications
The authorization boundary for approval ownership is missing from a route that records another principal's consent.
Controls and mitigations
- Require an explicit approval scope and ownership check on both read and decision routes, independent of CSRF and login.
- Verify the final executor rejects actions lacking a valid effect-bound approval receipt, even if an approval database row was modified.
Unknowns and contradictions
- 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.
Sources and citation
Material revision history
- Nov 15, 2026 · Canonical change recorded · new in release · revision 250