Go to packages list

payloadcms-storage-s3

Ecosystem: npm

Downloads: 1.8 Mln

Vulnerabilities from the last (months)
  • 0CriticalAffects 0 versions
  • 1HighAffects 2 versions
  • 0MediumAffects 0 versions
  • 1ModerateAffects 1 version
  • 0LowAffects 0 versions
Severity distribution (all time)
2vulnerabilities
  • Critical0 (0.0%)
  • High1 (50.0%)
  • Medium0 (0.0%)
  • Moderate1 (50.0%)
  • Low0 (0.0%)

Monthly breakdown

  • Critical
  • High
  • Medium
  • Moderate
  • Low
  • 1 vulnerabilities
    • Critical: 0
    • High: 1
    • Medium: 0
    • Moderate: 0
    • Low: 0
  • 1 vulnerabilities
    • Critical: 0
    • High: 0
    • Medium: 0
    • Moderate: 1
    • Low: 0

Vulnerabilities (2)

Known vulnerabilities affecting payloadcms-storage-s3, based on data from OSV.

Vulnerabilities affecting payloadcms-storage-s3
IDSeveritySummaryAffected versionsPublishedSource
GHSA-7vg8-29qx-jgj8HighPayload: Client uploads could overwrite S3 objects### Impact An authenticated user could overwrite an existing S3 object belonging to another upload collection, bypassing that collection’s access controls and prior file validation. You are affected if ALL of these are true: - Client uploads are enabled for multiple collections that share an S3 bucket. - useCompositePrefixes is not configured or is set to `false`. ### Patches Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`. ### Workarounds Disable client uploads until you can upgrade.
  • < 3.90.0
  • >= 4.0.0-canary.0, < 4.0.0-canary.34
GitHub (opens in a new tab)
GHSA-frq9-7j6g-v74xModeratePayload has Insufficient Filename Validation in Client-Upload Signed-URL Endpoints### Impact The client-upload signed-URL endpoints for S3, GCS, Azure, and R2 did not properly sanitize filenames. An attacker could craft filenames to escape the intended storage location. Consumers are affected if ALL of these are true: - Payload version **< v3.78.0** - Using client-upload signed-URL endpoints for any supported storage adapter ## Patches This vulnerability has been patched in **v3.78.0**. Filename validation has been hardened for client uploads. Consumers should upgrade to **v3.78.0** or later. ## Workarounds Consumers can upgrade: - Limit access to client-upload s
  • < 3.78.0
GitHub (opens in a new tab)
  • GHSA-7vg8-29qx-jgj8High
    Payload: Client uploads could overwrite S3 objects
    • < 3.90.0
    • >= 4.0.0-canary.0, < 4.0.0-canary.34
    GitHub (opens in a new tab)

    ### Impact An authenticated user could overwrite an existing S3 object belonging to another upload collection, bypassing that collection’s access controls and prior file validation. You are affected if ALL of these are true: - Client uploads are enabled for multiple collections that share an S3 bucket. - useCompositePrefixes is not configured or is set to `false`. ### Patches Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`. ### Workarounds Disable client uploads until you can upgrade.

    CVE: CVE-2026-105867

  • GHSA-frq9-7j6g-v74xModerate
    Payload has Insufficient Filename Validation in Client-Upload Signed-URL Endpoints
    • < 3.78.0
    GitHub (opens in a new tab)

    ### Impact The client-upload signed-URL endpoints for S3, GCS, Azure, and R2 did not properly sanitize filenames. An attacker could craft filenames to escape the intended storage location. Consumers are affected if ALL of these are true: - Payload version **< v3.78.0** - Using client-upload signed-URL endpoints for any supported storage adapter ## Patches This vulnerability has been patched in **v3.78.0**. Filename validation has been hardened for client uploads. Consumers should upgrade to **v3.78.0** or later. ## Workarounds Consumers can upgrade: - Limit access to client-upload s

    CVE: CVE-2026-34750

Showing 1-2 of 2 vulnerabilities