Approved changes feed: RSS · Atom

cpe:2.3:a:gatsbyjs:gatsby:*:*:*:*:*:node.js:*:*

part: a version: * update: *

VendorGatsbyjs (5329b80d-2167-5647-af74-9962ea542370)
ProductGatsby (87e241f2-adf3-51e8-abc7-35e6adc0f596)
Edition*
Language*
Software edition*
Target softwarenode.js
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/gatsbyjs/gatsby purl2cpe 2026-06-01 10:15:39.703247
pkg:npm/gatsby purl2cpe 2026-06-01 10:15:39.703250
pkg:sourceforge/gatsby.mirror purl2cpe 2026-06-01 10:15:39.703251

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2023-34238 vulnerable 2026-06-08 06:06:24.922830 Local File Inclusion vulnerability in Gatsby
MEDIUM (4.3)
Gatsby is a free and open source framework based on React. The Gatsby framework prior to versions 4.25.7 and 5.9.1 contain a Local File Inclusion vulnerability in the `__file-code-frame` and `__original-stack-frame` paths, exposed when running the Gatsby develop server (`gatsby develop`). Any file in scope of the development server could potentially be exposed. It should be noted that by default `gatsby develop` is only accessible via the localhost `127.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 the `GATSBY_HOST=0.0.0.0` environment variable. A patch has been introduced in `gatsby@5.9.1` and `gatsby@4.25.7` which mitigates the issue. Users are advised to upgrade. Users unable to upgrade should avoid exposing their development server to the internet.
Published: 2023-06-07T23:24:49.724Z
Updated: 2025-01-06T20:32:10.440Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-30548 vulnerable 2026-06-08 06:04:39.855702 Path traversal vulnerability in gatsby-plugin-sharp
MEDIUM (4.3)
gatsby-plugin-sharp is a plugin for the gatsby framework which exposes functions built on the Sharp image processing library. 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`). It should be noted that by default gatsby develop is only accessible via the localhost 127.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 the GATSBY_HOST=0.0.0.0 environment variable. Attackers exploiting this vulnerability will have read access to all files within the scope of the server process. A patch has been introduced in gatsby-plugin-sharp@5.8.1 and gatsby-plugin-sharp@4.25.1 which mitigates the issue by ensuring that included paths remain within the project directory. As stated above, by default gatsby develop is only exposed to the localhost 127.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. Users are non the less encouraged to upgrade to a safe version.
Published: 2023-04-17T20:43:43.033Z
Updated: 2025-02-05T20:34:27.816Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2023-22491 vulnerable 2026-06-08 05:54:26.426500 gatsby-transformer-remark vulnerable to unsanitized JavaScript code injection
HIGH (8.1)
Gatsby is a free and open source framework based on React that helps developers build websites and apps. The gatsby-transformer-remark plugin prior to versions 5.25.1 and 6.3.2 passes input through to the `gray-matter` npm package, which is vulnerable to JavaScript injection in its default configuration, unless input is sanitized. The vulnerability is present in gatsby-transformer-remark when passing input in data mode (querying MarkdownRemark nodes via GraphQL). Injected JavaScript executes in the context of the build server. To exploit this vulnerability untrusted/unsanitized input would need to be sourced by or added into a file processed by gatsby-transformer-remark. A patch has been introduced in `gatsby-transformer-remark@5.25.1` and `gatsby-transformer-remark@6.3.2` which mitigates the issue by disabling the `gray-matter` JavaScript Frontmatter engine. As a workaround, if an older version of `gatsby-transformer-remark` must be used, input passed into the plugin should be sanitized ahead of processing. It is encouraged for 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.
Published: 2023-01-13T18:05:00.273Z
Updated: 2025-03-11T13:34:01.261Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2022-25863 vulnerable 2026-06-08 05:41:49.584471 Deserialization of Untrusted Data
HIGH (8.1)
The package gatsby-plugin-mdx before 2.14.1, from 3.0.0 and before 3.15.2 are vulnerable to Deserialization of Untrusted Data when passing input through to the gray-matter package, due to its default configurations that are missing input sanitization. Exploiting this vulnerability is possible when passing input in both webpack (MDX files in src/pages or MDX file imported as a component in frontend / React code) and data mode (querying MDX nodes via GraphQL). Workaround: If an older version of gatsby-plugin-mdx must be used, input passed into the plugin should be sanitized ahead of processing.
Published: 2022-06-10T20:00:19.275Z
Updated: 2024-09-17T00:31:34.621Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.