fix(deps): update dependency gatsby-plugin-sharp to v4.25.1 [security] - #309
Open
renovate[bot] wants to merge 1 commit into
Open
fix(deps): update dependency gatsby-plugin-sharp to v4.25.1 [security]#309renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
renovate
Bot
deleted the
renovate/npm-gatsby-plugin-sharp-vulnerability
branch
September 21, 2023 12:24
renovate
Bot
restored the
renovate/npm-gatsby-plugin-sharp-vulnerability
branch
September 21, 2023 15:29
renovate
Bot
force-pushed
the
renovate/npm-gatsby-plugin-sharp-vulnerability
branch
from
September 21, 2023 15:30
3e57392 to
4632819
Compare
renovate
Bot
force-pushed
the
renovate/npm-gatsby-plugin-sharp-vulnerability
branch
from
August 10, 2025 15:09
4632819 to
ceb9673
Compare
renovate
Bot
force-pushed
the
renovate/npm-gatsby-plugin-sharp-vulnerability
branch
from
November 10, 2025 15:44
ceb9673 to
f5c0089
Compare
renovate
Bot
force-pushed
the
renovate/npm-gatsby-plugin-sharp-vulnerability
branch
from
November 18, 2025 10:39
f5c0089 to
a038a2e
Compare
renovate
Bot
force-pushed
the
renovate/npm-gatsby-plugin-sharp-vulnerability
branch
from
December 3, 2025 18:14
a038a2e to
16ae289
Compare
renovate
Bot
force-pushed
the
renovate/npm-gatsby-plugin-sharp-vulnerability
branch
from
December 31, 2025 16:33
16ae289 to
a51e6e4
Compare
renovate
Bot
force-pushed
the
renovate/npm-gatsby-plugin-sharp-vulnerability
branch
from
February 12, 2026 16:07
a51e6e4 to
e728017
Compare
renovate
Bot
force-pushed
the
renovate/npm-gatsby-plugin-sharp-vulnerability
branch
from
March 5, 2026 17:30
e728017 to
291222e
Compare
renovate
Bot
force-pushed
the
renovate/npm-gatsby-plugin-sharp-vulnerability
branch
from
March 30, 2026 17:33
affb136 to
291222e
Compare
renovate
Bot
force-pushed
the
renovate/npm-gatsby-plugin-sharp-vulnerability
branch
from
March 30, 2026 17:34
291222e to
affb136
Compare
renovate
Bot
force-pushed
the
renovate/npm-gatsby-plugin-sharp-vulnerability
branch
from
May 28, 2026 18:17
affb136 to
34fd5e2
Compare
renovate
Bot
force-pushed
the
renovate/npm-gatsby-plugin-sharp-vulnerability
branch
from
June 1, 2026 22:52
34fd5e2 to
7f44036
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.21.0→4.25.1Path traversal vulnerability in gatsby-plugin-sharp
CVE-2023-30548 / GHSA-h2pm-378c-pcxx
More information
Details
Impact
The gatsby-plugin-sharp plugin prior to versions 5.8.1 and 4.25.1 contains a path traversal vulnerability exposed when running the Gatsby develop server (
gatsby develop).The following steps can be used to reproduce the vulnerability:
It should be noted that by default
gatsby developis only accessible via the localhost127.0.0.1, and one would need to intentionally expose the server to other interfaces to exploit this vulnerability by using server options such as--host 0.0.0.0,-H 0.0.0.0, or theGATSBY_HOST=0.0.0.0environment variable.Patches
A patch has been introduced in
gatsby-plugin-sharp@5.8.1andgatsby-plugin-sharp@4.25.1which mitigates the issue by ensuring that included paths remain within the project directory.Workarounds
As stated above, by default
gatsby developis only exposed to the localhost127.0.0.1. For those using the develop server in the default configuration no risk is posed. If other ranges are required, preventing the develop server from being exposed to untrusted interfaces or IP address ranges would mitigate the risk from this vulnerability.We encourage projects to upgrade to the latest major release branch for all Gatsby plugins to ensure the latest security updates and bug fixes are received in a timely manner.
Credits
We would like to thank Patrick Rombouts and Bart Veneman [drukwerkdeal.nl] for bringing the issue to our attention.
For more information
Email us at security@gatsbyjs.com.
Severity
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
gatsbyjs/gatsby (gatsby-plugin-sharp)
v4.25.1Compare Source
v4.25.0Compare Source
v4.24.0Compare Source
🧾 Release notes
Note: Version bump only for package gatsby-plugin-sharp
4.23.1 (2022-09-22)
Note: Version bump only for package gatsby-plugin-sharp
v4.23.1Compare Source
🧾 Release notes
Note: Version bump only for package gatsby-plugin-sharp
4.23.1 (2022-09-22)
Note: Version bump only for package gatsby-plugin-sharp
v4.23.0Compare Source
🧾 Release notes
Chores
v4.22.0Compare Source
🧾 Release notes
Chores
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.