Skip to content

fix(workflows): Check workflow permissions before attaching detectors - #124861

Draft
shashjar wants to merge 1 commit into
masterfrom
shashjar/check-workflow-permissions-before-attaching-detectors
Draft

shashjar wants to merge 1 commit into
masterfrom
shashjar/check-workflow-permissions-before-attaching-detectors

Conversation

@shashjar

Copy link
Copy Markdown
Member

Fixes https://linear.app/getsentry/issue/ISWF-2862/warden-finding-detector-createupdate-can-attach-inaccessible-workflows & https://linear.app/getsentry/issue/VULN-1848/security-detector-createupdate-can-attach-inaccessible-workflows.

Detector create and update now require access and write permission for each newly attached workflow. Previously, validation only checked that workflow IDs belonged to the organization.

Reuse the workflow endpoint’s permission rules during serializer validation and connection creation. Existing connections can still be retained or removed with detector permissions.

@linear-code

linear-code Bot commented Sep 17, 2026

Copy link
Copy Markdown

VULN-1848

ISWF-2862

@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label Sep 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant