Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9

Craft CMS Vulnerable to SSRF in GraphQL Asset Mutation via Alternative IP Notation

CVE-2026-25494GHSA-m5r2-8p9x-hp5m

What to do

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

Add to your agent

Affected packages

  • Packagist craftcms/cms

    Affected
    >= 5.0.0-RC1, <= 5.8.21>= 4.0.0-RC1, <= 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
6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X · score source
EPSS
  • CVE-2026-25494: 0.40% estimated exploitation activity in the next 30 days; percentile 34.68 (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.

I observed a recent commit intended to mitigate Server-Side Request Forgery (SSRF) vulnerabilities. While the implemented defense mechanisms are an improvement, I have identified two methods to bypass these protections. This report details the first bypass method involving alternative IP notation, while the second method will be submitted in a separate advisory. --- Summary The saveAsset GraphQL mutation uses filtervar(..., FILTERVALIDATEIP) to block a specific list of IP addresses. However, alternative IP notations (hexadecimal, mixed) are not recognized by this function, allowing attackers to bypass the blocklist and access cloud metadata services. --- Proof of Concept 1. Send the following GraphQL mutation: 2. The IP validation passes (hex notation not recognized as IP) 3. Guzzle resolves 169.254.0xa9fe to 169.254.169.254 4. Cloud metadata is fetched and saved Alternative Payloads | Payload | Notation | Resolves To | |---------|----------|-------------| | http://169.254.0xa9fe/ |…

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

    Published from ghsa record GHSA-m5r2-8p9x-hp5m

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

Advisory: Craft CMS Vulnerable to SSRF in GraphQL Asset Mutation via Alternative IP Notation
IDs: CVE-2026-25494, GHSA-m5r2-8p9x-hp5m
Record: https://patchnext.com/advisories/cve-2026-25494 (revision 1, source checked 26 Oct 2026, 14:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: craftcms/cms 5.8.22, 4.16.18. A vendor fix does not mean a deployment is fixed.

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

## Suggested inspection (read-only)
- Packagist craftcms/cms: 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/cms.
- 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-m5r2-8p9x-hp5m (GitHub-reviewed advisory GHSA-m5r2-8p9x-hp5m lists affected ranges: Packagist craftcms/cms >=5.0.0-RC1 =4.0.0-RC1 <=4.16.17)

Commands are suggestions: review each one before running it.

Loading voting…