Skip to content

fix: Protected fields leak via LiveQuery afterEvent trigger (GHSA-5hmj-jcgp-6hff)#10233

Merged
mtrezza merged 1 commit intoparse-community:release-8.x.xfrom
mtrezza:fix/GHSA-5hmj-jcgp-6hff-v8
Mar 17, 2026
Merged

fix: Protected fields leak via LiveQuery afterEvent trigger (GHSA-5hmj-jcgp-6hff)#10233
mtrezza merged 1 commit intoparse-community:release-8.x.xfrom
mtrezza:fix/GHSA-5hmj-jcgp-6hff-v8

Conversation

@mtrezza
Copy link
Member

@mtrezza mtrezza commented Mar 17, 2026

Issue

Protected fields leak via LiveQuery afterEvent trigger (GHSA-5hmj-jcgp-6hff)

Tasks

  • Add new tests
  • Add changes to documentation (guides, migration guide)
  • Add entry to changelog
  • Security check
  • Benchmark check
  • Breaking change

@parse-github-assistant
Copy link

parse-github-assistant bot commented Mar 17, 2026

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Tip

  • Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
  • Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
  • Group code into logical blocks. Add a short comment before each block to explain its purpose.
  • We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
  • Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
  • Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement.

@parseplatformorg
Copy link
Contributor

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@coderabbitai
Copy link

coderabbitai bot commented Mar 17, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 68e522a6-2a10-4514-b15e-7d52368da0ee

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
📝 Coding Plan
  • Generate coding plan for human review comments

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 and usage tips.

@codecov
Copy link

codecov bot commented Mar 17, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.48%. Comparing base (b62336b) to head (f8b8c63).
⚠️ Report is 3 commits behind head on release-8.x.x.

Additional details and impacted files
@@              Coverage Diff               @@
##           release-8.x.x   #10233   +/-   ##
==============================================
  Coverage          92.48%   92.48%           
==============================================
  Files                192      192           
  Lines              15932    15938    +6     
  Branches             196      197    +1     
==============================================
+ Hits               14735    14741    +6     
  Misses              1180     1180           
  Partials              17       17           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@mtrezza mtrezza changed the title fix: GHSA-5hmj-jcgp-6hff v8 fix: Protected fields leak via LiveQuery afterEvent trigger (GHSA-5hmj-jcgp-6hff) Mar 17, 2026
@mtrezza mtrezza merged commit 743324e into parse-community:release-8.x.x Mar 17, 2026
26 of 28 checks passed
parseplatformorg pushed a commit that referenced this pull request Mar 17, 2026
## [8.6.50](8.6.49...8.6.50) (2026-03-17)

### Bug Fixes

* Protected fields leak via LiveQuery afterEvent trigger ([GHSA-5hmj-jcgp-6hff](GHSA-5hmj-jcgp-6hff)) ([#10233](#10233)) ([743324e](743324e))
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 8.6.50

@parseplatformorg parseplatformorg added the state:released-8.x.x Released as LTS version label Mar 17, 2026
@mtrezza mtrezza deleted the fix/GHSA-5hmj-jcgp-6hff-v8 branch March 18, 2026 00:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

state:released-8.x.x Released as LTS version

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants