Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.6amended

ApostropheCMS uploadfs Azure backend leaks account-level SAS token into every public attachment URL (sas: true)

CVE-2026-113652GHSA-hhph-8536-gfq5

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (uploadfs 1.28.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm uploadfs

    Affected
    >= 1.25.0, < 1.28.0
    Fixed in
    1.28.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.6 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS
  • CVE-2026-113652: 0.28% estimated exploitation activity in the next 30 days; percentile 20.26 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary When uploadfs is configured with the Azure backend and sas: true (a supported configuration introduced in uploadfs 1.25.0), createContainer() builds the BlobServiceClient from a URL that embeds the full SAS query string, and Azure SDK v12 derived clients inherit that query string. As a result, getUrl() returns a base URL carrying the complete account/container SAS signature (?sv=...&sig=...), and Apostrophe's attachment.url() prepends it to every public attachment link — broadcasting a container-level SAS credential (commonly sp=rwdlac, full read/write/delete/list) to every site visitor, including anonymous ones. Anyone who can see an attachment URL can read, overwrite, delete, and list every blob in the container for the SAS lifetime. A companion functional bug (blob path appended after the query string, producing broken URLs) shows this code path was never exercised end to end. Shared-key mode (default) and non-Azure backends are not affected. Verified at commit…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-hhph-8536-gfq5

  2. Revision 2 · amended ·

    Amended from osv record GHSA-hhph-8536-gfq5

  3. Revision 1 · created ·

    Published from ghsa record GHSA-hhph-8536-gfq5

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-113652

Advisory: ApostropheCMS uploadfs Azure backend leaks account-level SAS token into every public attachment URL (sas: true)
IDs: CVE-2026-113652, GHSA-hhph-8536-gfq5
Record: https://patchnext.com/advisories/cve-2026-113652 (revision 3, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: uploadfs 1.28.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm uploadfs: affected >= 1.25.0, < 1.28.0; fixed in 1.28.0

## Suggested inspection (read-only)
- `npm ls uploadfs --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on uploadfs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hhph-8536-gfq5 (GitHub-reviewed advisory GHSA-hhph-8536-gfq5 lists affected ranges: npm uploadfs >=1.25.0 <1.28.0)
- Verified: https://osv.dev/vulnerability/GHSA-hhph-8536-gfq5 (OSV record GHSA-hhph-8536-gfq5 lists affected ranges: npm uploadfs >=1.25.0 <1.28.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…