Skip to content

Fixed Flase Positive | Next.js - Cache Poisoning - Headers #11532

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jan 28, 2025
Merged

Fixed Flase Positive | Next.js - Cache Poisoning - Headers #11532

merged 1 commit into from
Jan 28, 2025

Conversation

@princechaddha
Copy link
Member

@princechaddha princechaddha commented Jan 25, 2025

Template / PR Information

  • Fixed CVE-2020-XXX / Added CVE-2020-XXX / Updated CVE-2020-XXX
  • References:

Template Validation

I've validated this template locally?

  • YES
  • NO

Additional Details (leave it blank if not applicable)

Additional References:

@princechaddha princechaddha added the Done Ready to merge label Jan 25, 2025
@princechaddha princechaddha linked an issue Jan 25, 2025 that may be closed by this pull request
[FALSE-POSITIVE] Next.js - Cache Poisoning - Headers #11473
Closed
@DhiyaneshGeek DhiyaneshGeek merged commit 627c875 into main Jan 28, 2025
4 checks passed
@DhiyaneshGeek DhiyaneshGeek deleted the fixed-fp-nextjs-rsc-cache branch January 28, 2025 12:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@DhiyaneshGeek DhiyaneshGeek DhiyaneshGeek approved these changes

Assignees

@ritikchaddha ritikchaddha

Labels

Done Ready to merge

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[FALSE-POSITIVE] Next.js - Cache Poisoning - Headers

4 participants

@princechaddha @DhiyaneshGeek @ritikchaddha