ultraworkers / ultraworkers/claw-code

Security: private coordinated disclosure ready (enable PVR or contact @macncrash)

Open
#3,276 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
195k
Forks
108k
PR merge metrics
No merged PRs in 30d

Description

Coordination request (no technical details here)

I have a private coordinated vulnerability report for ultraworkers/claw-code affecting sandbox isolation reporting and permission-mode persistence (HIGH). Report includes full write-up and suggested patches.

Private vulnerability reporting appears disabled on this repository (GET .../private-vulnerability-reportingenabled: false), so I cannot file a GHSA report via the API.

Please either
  1. Enable private vulnerability reporting so I can submit the full package via GitHub Security Advisories, or
  2. Contact @macncrash / macncrash@users.noreply.github.com and I will grant access to the private package repo or re-send the materials.

Private package (invite-only): https://github.com/macncrash/saudit-disclosure-claw-code-2026-07

I will not post exploit details, PoCs, or patches on this public issue.

Reporter: macncrash
AI-assisted analysis; findings human-verified. Local validation only.

Thank you.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no repository files, tests, or code entry points. Start by reviewing the repository's GitHub Security Advisories and private vulnerability reporting settings, then consult the linked private disclosure package; done means the reporter can submit the report or receives maintainer contact.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.