Skip to content

[Snyk] Security upgrade electron from 13.6.8 to 17.4.11#2

Open
snyk-bot wants to merge 1 commit into
masterfrom
snyk-fix-a5b198ed1a6d9b262c70a6f073ce29f6
Open

[Snyk] Security upgrade electron from 13.6.8 to 17.4.11#2
snyk-bot wants to merge 1 commit into
masterfrom
snyk-fix-a5b198ed1a6d9b262c70a6f073ce29f6

Conversation

@snyk-bot

Copy link
Copy Markdown

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • electron_app/package.json
    • electron_app/package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 809/1000
Why? Mature exploit, Has a fix available, CVSS 7.6
Use After Free
SNYK-JS-ELECTRON-2414027
Yes Mature
high severity 794/1000
Why? Mature exploit, Has a fix available, CVSS 7.3
Type Confusion
SNYK-JS-ELECTRON-2434822
Yes Mature
critical severity 919/1000
Why? Mature exploit, Has a fix available, CVSS 9.8
Type Confusion
SNYK-JS-ELECTRON-2805803
Yes Mature
high severity 859/1000
Why? Mature exploit, Has a fix available, CVSS 8.6
Heap-based Buffer Overflow
SNYK-JS-ELECTRON-2946881
Yes Mature

(*) Note that the real score may have changed since the PR was raised.

Check the changes in this PR to ensure they won't cause issues with your project.


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@mergify

mergify Bot commented Aug 17, 2025

Copy link
Copy Markdown

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #2 has been dequeued. The pull request rule doesn't match anymore.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

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.

1 participant