Skip to content

fix(security): disable dangerouslyAllowSVG in Next.js image optimization pipeline - #2711

Open
tmdeveloper007 wants to merge 1 commit into
nisshchayarathi:mainfrom
tmdeveloper007:fix/2646-disable-svg-images
Open

fix(security): disable dangerouslyAllowSVG in Next.js image optimization pipeline#2711
tmdeveloper007 wants to merge 1 commit into
nisshchayarathi:mainfrom
tmdeveloper007:fix/2646-disable-svg-images

Conversation

@tmdeveloper007

Copy link
Copy Markdown
Contributor

Description

next.config.js had dangerouslyAllowSVG: true in the images configuration. While a CSP header (script-src 'none'; sandbox;) is present, SVG files served through Next.js image optimization can be vectors for XSS attacks when users control repository avatars, file previews, or other image sources.

Fix: set dangerouslyAllowSVG: false. If the application legitimately needs to optimize SVG images in the future, this can be re-enabled with additional safeguards.

Related Issues

Type of Change

  • Bug fix (non-breaking change that fixes an issue)

Checklist

  • Code compiles and passes existing tests
  • Changes are minimal and targeted at the reported security issue

@vercel

vercel Bot commented Aug 3, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the Nisshchaya's projects Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

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

Next review available in: 56 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: d5678d60-ec0f-4e43-872d-dfcc0edcd179

📥 Commits

Reviewing files that changed from the base of the PR and between 153f57d and 4a5b026.

📒 Files selected for processing (1)
  • next.config.js

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.

@github-actions

github-actions Bot commented Aug 3, 2026

Copy link
Copy Markdown

⚠️ GSSoC Quality Check Failed — PR #2711

Hi @tmdeveloper007! 👋 Your PR has been flagged by our automated GSSoC quality check.

Issues found:

  • 📏 Trivially small change — Only 2 line(s) changed in 1 file. Changes this small are almost never meaningful contributions. Make sure your PR solves a real issue.

✅ How to fix this

  1. Read the issues listed above carefully
  2. Edit your PR title and description to address them
  3. Make sure your PR is linked to an open issue using closes #<issue-number>
  4. Make sure your changes are meaningful and solve a real problem

Once you've fixed these, a maintainer will review and remove the flag. If you believe this is a mistake, please comment below. 🙏

GSSoC'26 automation · Maintainer: @nisshchayarathi

@github-actions github-actions Bot added the gssoc:spam GSSoC: Spam contribution label Aug 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gssoc:spam GSSoC: Spam contribution

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Security: dangerouslyAllowSVG enabled in Next.js image optimization pipeline

1 participant