auth refresh endpoint issues tokens without verifying the requester
Open-source bounty · GitHub (bounty labels) · open as of 17 Oct 2026
- Amount as listed
- $780 fixed “$780” — quoted from GitHub (bounty labels)
- Platform
- GitHub (bounty labels)
- Kind of work
- Open-source bounty · Engineering
- Open to
- not stated by the platform
- Deadline
- not stated by the platform
- Status
- Open
- Checked
- 17 Oct 2026, 18:16 UTC
What the listing says
Bug POST /api/auth/refresh currently issues a fresh access token without checking the requester at all. The service also signs that token for the hard-coded subject usr existing with role client, so even an authenticated caller does not get a token for their own subject and role. Expected fix Protect the refresh route
Excerpt we recorded when we checked: Etiketten: 💎 Bounty, bug, enhancement, good first issue, help wanted, bug bounty, AI agent friendly, bounty, 💎 Bounty, $780
Open on GitHub (bounty labels) ↗
The work is offered, scoped and paid by GitHub (bounty labels) — not by GOAT Market. We record what they publish and link to it. Claiming, delivering and getting paid all happen on their site, under their terms.
More open on GitHub (bounty labels)
- [Feature] Implement Basic Anti-Cheat Protection $10,000
- [ Bounty $9k ] [ SDK ] Fix encoding.ts decodeParameter doesn't handle dynamic types — back... $9,000
- [ Bounty $9k ] [ Solidity ] Add gas sponsorship relay for agent transactions — security cr... $9,000
- [ Bounty $9k ] [ API ] Fix agents.py doesn't validate endpoint URL format — testnet findin... $9,000
- [ Bounty $9k ] [ SDK ] Fix rpc.ts doesn't handle JSON-RPC batch response ordering — backwa... $9,000