CVE-2026-39397

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 9.4 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-04-08) is not newer than that change (2026-07-24), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-19921 (ENISA EUVD) · GHSA-65w6-pf7x-5g85 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

@delmaredigital/payload-puck is a PayloadCMS plugin for integrating Puck visual page builder. Prior to 0.6.23, all /api/puck/* CRUD endpoint handlers registered by createPuckPlugin() called Payload's local API with the default overrideAccess: true, bypassing all collection-level access control. The access option passed to createPuckPlugin() and any access rules defined on Puck-registered collections were silently ignored on these endpoints. This vulnerability is fixed in 0.6.23.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
33rd
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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 7, 2026

Last Modified

July 24, 2026

Advisory Details (3)

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

Missing authorization on /api/puck/* CRUD endpoints allows unauthenticated access to Puck-registered collections · Advisory · delmaredigital/payload-puck · GitHub

https://github.com/delmaredigital/payload-puck/security/advisories/GHSA-65w6-pf7x-5g85
Web page

Access control on /api/puck endpoints · Issue #7 · delmaredigital/payload-puck · GitHub

https://github.com/delmaredigital/payload-puck/issues/7
GitHub commit Patch Available

commit 9148201c6bbf (delmaredigital/payload-puck)

Patch available: delmaredigital/payload-puck v0.6.23 (contains commit 9148201c6bbf)

https://github.com/delmaredigital/payload-puck/commit/9148201c6bbfa140d44546438027a2f8a70f79a4

Vendor Advisories for CVE-2026-39397(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@delmaredigital/payload-puck @ 0.6.23 (fixes < 0.6.23)—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
@delmaredigital/payload-puck—
  • every version up to 0.6.23: fixed in 0.6.23
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 43× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 263 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 163 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-39397?
CVE-2026-39397 is a critical-severity vulnerability; its CVE record was published on April 7, 2026. @delmaredigital/payload-puck is a PayloadCMS plugin for integrating Puck visual page builder. Prior to 0.6.23, all /api/puck/* CRUD endpoint handlers registered by createPuckPlugin() called Payload's local API with the default overrideAccess: true, bypassing all collection-level access control. The…
When was the CVE record for CVE-2026-39397 published?
The CVE record for CVE-2026-39397 was published on April 7, 2026. 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 July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-39397 actively exploited?
CVE-2026-39397 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-39397?
CVE-2026-39397 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-39397?
A fix for CVE-2026-39397 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-39397 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-39397

Explore →

Is Your Infrastructure Affected by CVE-2026-39397?

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

Book a Demo →Browse All CVEs