Skip to content

← Actionable
Medium, CVSS 5.3

Craft CMS: save_images_Asset graphql mutation can be abused to exfiltrate AWS credentials of underlying host

CVE-2026-25492GHSA-96pq-hxpw-rgh8

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (craftcms/craft 5.8.22, 4.16.18), 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.

Affected packages

  • Packagist craftcms/craft

    Affected
    >= 5.0.0-RC1, <= 5.8.21>= 3.5.0, <= 4.16.17
    Fixed in
    5.8.22, 4.16.18

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-25492: 0.47% estimated exploitation activity in the next 30 days; percentile 40.88 (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 - The saveimagesAsset graphql mutation allows a user to give a url of an image to download. (Url must use a domain, not a raw IP.) - Attacker sets up domain attacker.domain with an A record of something like 169.254.169.254 (special AWS metadata IP) - Attacker invokes saveimagesAsset with url: http://attacker.domain/latest/meta-data/iam/security-credentials and filename "foo.txt" - Craft fetches sensitive information on attacker's behalf, and makes it available for download at /assets/images/foo.txt - Normal checks to verify that image is valid are bypassed because of .txt extension - Normal checks to verify that url is not an IP address are bypassed because user provided a valid domain that resolves to a sensitive internal IP address Details handleUpload() in src/gql/resolvers/mutations/Assets.php contains the code that processes the saveimagesAsset mutation. It has some basic validation logic for the url parameter (source of the image) and filename parameter (what to save…

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

    Published from ghsa record GHSA-96pq-hxpw-rgh8

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-25492

Advisory: Craft CMS: save_images_Asset graphql mutation can be abused to exfiltrate AWS credentials of underlying host
IDs: CVE-2026-25492, GHSA-96pq-hxpw-rgh8
Record: https://patchnext.com/advisories/cve-2026-25492 (revision 1, source checked 26 Oct 2026, 14:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: craftcms/craft 5.8.22, 4.16.18. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist craftcms/craft: affected >= 5.0.0-RC1, <= 5.8.21; >= 3.5.0, <= 4.16.17; fixed in 5.8.22, 4.16.18

## Suggested inspection (read-only)
- Packagist craftcms/craft: check the installed version with your package manager.

## 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 craftcms/craft.
- 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-96pq-hxpw-rgh8 (GitHub-reviewed advisory GHSA-96pq-hxpw-rgh8 lists affected ranges: Packagist craftcms/craft >=5.0.0-RC1 =3.5.0 <=4.16.17)

Commands are suggestions: review each one before running it.

Loading voting…