Skip to content

fix(api): cap the GitHub webhook request body size#353

Open
cavidelizade wants to merge 1 commit into
Devlaner:mainfrom
cavidelizade:fix/webhook-body-limit
Open

fix(api): cap the GitHub webhook request body size#353
cavidelizade wants to merge 1 commit into
Devlaner:mainfrom
cavidelizade:fix/webhook-body-limit

Conversation

@cavidelizade

Copy link
Copy Markdown
Contributor

Summary

The GitHub webhook receiver read the whole request body with io.ReadAll and no size limit, before checking the signature, on a public unauthenticated route. A single large POST, or a few concurrent ones, could exhaust process memory.

Linked issues

Closes #329

Type of change

  • Bug fix (fix:)

Surface

  • API (apps/api/)

What changed

Wrap c.Request.Body in http.MaxBytesReader at GitHub's 25 MiB payload cap before reading, and return 413 when it's exceeded.

Test plan

  • go build, go vet, go test ./... green
  • Reasoning: a body over 25 MiB now fails the read with a MaxBytesError and returns 413 instead of being buffered in full

AI assistance

  • AI tools were used, tool(s): Claude Code (Opus 4.8), commits carry a Co-Authored-By: trailer

The webhook receiver read the entire request body with io.ReadAll and no size
limit, before checking the signature, on a public unauthenticated route. A
single large POST (or a few concurrent ones) could exhaust process memory.

Wrap the body in http.MaxBytesReader at GitHub's 25 MiB payload cap and return
413 when it's exceeded.

Closes Devlaner#329

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@cavidelizade
cavidelizade requested a review from a team as a code owner July 16, 2026 20:10
@coderabbitai

coderabbitai Bot commented Jul 16, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@cavidelizade, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 51 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 15cc6b4e-059d-4fa5-9764-82c9187bc868

📥 Commits

Reviewing files that changed from the base of the PR and between 61bc903 and e3cc7c1.

📒 Files selected for processing (1)
  • apps/api/internal/handler/integration.go
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GitHub webhook endpoint reads the request body with no size limit (DoS)

1 participant