CVE-2023-30548

MEDIUMNVD 4.34.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 4.3 from GitHub Security Advisory (severity: MODERATE) published 2023-04-20. NVD baseline CVSS 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2023-1316 (ENISA EUVD) · GHSA-h2pm-378c-pcxx (GitHub Security Advisories)Source: ENISA EUVD

4.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 4.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.9%
EPSS %ILE
59th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 17, 2023

Last Modified

September 29, 2026

Advisory Details (3)

Auto-updated Sep 29, 2026
Patch available. Sources: github, github_commit.
GitHub advisoryMentions a patch (unverified)

Path traversal vulnerability exposed by Gatsby develop server in gatsby-plugin-sharp · Advisory · gatsbyjs/gatsby · GitHub

https://github.com/gatsbyjs/gatsby/security/advisories/GHSA-h2pm-378c-pcxx
GitHub commit

commit dcf88ed01df2 (gatsbyjs/gatsby)

Fix landed in gatsbyjs/gatsby commit dcf88ed01df2 — awaiting tagged release

https://github.com/gatsbyjs/gatsby/commit/dcf88ed01df2c26e0c93a41e1a2a840076d8247e
GitHub commit

commit 5f442081b227 (gatsbyjs/gatsby)

Fix landed in gatsbyjs/gatsby commit 5f442081b227 — awaiting tagged release

https://github.com/gatsbyjs/gatsby/commit/5f442081b227cc0879babb96858f970c4ce94c6b

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmgatsby-plugin-sharp @ 5.8.1 (fixes >= 5.0.0, < 5.8.1)—ghsa
npmgatsby-plugin-sharp @ 4.25.1 (fixes < 4.25.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
gatsby-plugin-sharp—
  • 5.0.0 up to 5.8.1: fixed in 5.8.1
  • every version up to 4.25.1: fixed in 4.25.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 213 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:39 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  2. 2026-11-01 16:30 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  3. 2026-11-01 08:21 UTCGHSA enrichmentGHSA-h2pm-378c-pcxx · GitHub severity MODERATE · GitHub CVSS 4.3
  4. 2026-11-01 08:21 UTCEG score recompute
  5. 2026-10-31 16:29 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  6. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  7. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  8. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  9. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  10. 2026-10-26 16:28 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  11. 2026-10-25 17:43 UTCEG score recompute
  12. 2026-10-25 16:29 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  13. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  14. 2026-10-24 14:46 UTCEG score recompute
  15. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  16. 2026-10-22 21:25 UTCOSV refresh
  17. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  18. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  19. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  20. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  21. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  22. 2026-10-18 08:04 UTCEG score recompute
  23. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  24. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  25. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.9% · 58th percentile
Show 71 more
  1. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  2. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  3. 2026-10-12 18:28 UTCEG score recompute
  4. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  5. 2026-10-11 21:54 UTCEG score recompute
  6. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  7. 2026-10-10 19:57 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  8. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  9. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  10. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  11. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  12. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  13. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  14. 2026-10-02 16:23 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  15. 2026-10-01 19:47 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  16. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  17. 2026-09-29 15:51 UTCEG score recompute
  18. 2026-09-29 15:16 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  19. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  20. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  21. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  22. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  23. 2026-09-23 14:34 UTCOSV refresh
  24. 2026-09-23 13:45 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  25. 2026-09-22 14:45 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  26. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  27. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  28. 2026-09-13 16:44 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  29. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  30. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  31. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  32. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  33. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  34. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  35. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  36. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  37. 2026-09-04 09:16 UTCOSV refresh
  38. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  39. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  40. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  41. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  42. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  43. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  44. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  45. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  46. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  47. 2026-08-24 14:14 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  48. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  49. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  50. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  51. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  52. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  53. 2026-08-17 19:59 UTCOSV refresh
  54. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  55. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  56. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  57. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  58. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  59. 2026-08-11 13:39 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  60. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  61. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  62. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  63. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  64. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  65. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  66. 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  67. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  68. 2026-08-02 15:27 UTCOSV refresh
  69. 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  70. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  71. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.9% · 55th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-30548?
CVE-2023-30548 is a medium-severity vulnerability; its CVE record was published on April 17, 2023. 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…
When was the CVE record for CVE-2023-30548 published?
The CVE record for CVE-2023-30548 was published on April 17, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 29, 2026; the record at its source may have been updated since.
Is CVE-2023-30548 actively exploited?
CVE-2023-30548 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (59th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-30548?
CVE-2023-30548 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2023-30548?
A fix for CVE-2023-30548 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-30548

Explore →

Is Your Infrastructure Affected by CVE-2023-30548?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs