Skip to content

fix(rbac): give org members scope to run agents#2618

Merged
daryllimyt merged 1 commit intomainfrom
fix/rbac-llm-providers
May 5, 2026
Merged

fix(rbac): give org members scope to run agents#2618
daryllimyt merged 1 commit intomainfrom
fix/rbac-llm-providers

Conversation

@jordan-umusu
Copy link
Copy Markdown
Collaborator

@jordan-umusu jordan-umusu commented May 5, 2026

Summary by cubic

Allow organization members to run agents by adding the missing org:secret:read scope to the organization-member preset. This unblocks agent execution that needs org secrets.

  • Bug Fixes
    • Added org:secret:read to organization-member in PRESET_ROLE_SCOPES.
    • Added a unit test to verify members have agent:read, agent:execute, and org:secret:read.

Written for commit 87add39. Summary will update on new commits.

@jordan-umusu jordan-umusu marked this pull request as ready for review May 5, 2026 19:52
@jordan-umusu jordan-umusu temporarily deployed to internal-registry-ci May 5, 2026 19:52 — with GitHub Actions Inactive
@jordan-umusu jordan-umusu requested a review from daryllimyt May 5, 2026 19:52
@jordan-umusu jordan-umusu temporarily deployed to internal-registry-ci May 5, 2026 19:53 — with GitHub Actions Inactive
@jordan-umusu jordan-umusu added the priority:critical Critical priority ticket — drop everything label May 5, 2026
@zeropath-ai
Copy link
Copy Markdown

zeropath-ai Bot commented May 5, 2026

No security or compliance issues detected. Reviewed everything up to 87add39.

Security Overview
Detected Code Changes
Change Type Relevant files
Enhancement ► tests/unit/test_rbac_scopes.py
    Add test case for org:secret:read scope
► tracecat/authz/scopes.py
    Add org:secret:read scope to preset roles

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 2 files

Confidence score: 2/5

  • High-risk authorization change in tracecat/authz/scopes.py: granting org:secret:read to all organization members appears to exceed the intended scope (agent execution) and can expose org secrets to broader roles.
  • The issue is both high severity and high confidence (8/10 each), which suggests a concrete security regression rather than a minor policy tweak.
  • Pay close attention to tracecat/authz/scopes.py - permission scope expansion may over-grant secret read access and should be narrowed before merge.
Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="tracecat/authz/scopes.py">

<violation number="1" location="tracecat/authz/scopes.py:324">
P1: Adding `org:secret:read` to organization members over-grants access: members can now call org secret read endpoints, which is broader than the stated goal of enabling agent execution.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

Comment thread tracecat/authz/scopes.py
@daryllimyt daryllimyt merged commit 9edc922 into main May 5, 2026
16 of 17 checks passed
@daryllimyt daryllimyt deleted the fix/rbac-llm-providers branch May 5, 2026 20:05
@blacksmith-sh
Copy link
Copy Markdown
Contributor

blacksmith-sh Bot commented May 5, 2026

Blacksmith runners detected OOM events on the following jobs:

Job Details
test-all (temporal) View Job

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority:critical Critical priority ticket — drop everything

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants