# CVE-2026-130675: Craft CMS 5.0.0 before 5.11.4 RCE via Image Transform Class Guard Bypass


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-38f7-cj22-qv2v, GHSA-hq78-cm2m-h24h

## What is CVE-2026-130675?

CVE-2026-130675 is a critical vulnerability in craftcms cms, published on 18 Nov 2026. 

### Official description

Craft CMS from 5.0.0 before 5.11.4 contains a remote code execution vulnerability in ImageTransforms::normalizeTransform() that allows attackers to instantiate arbitrary classes by supplying class:null with a __class key. Attackers can reach the method through Craft Commerce's payments/pay redirect template calling customer.photo.getUrl() with a crafted transform to instantiate classes like yii\rbac\PhpManager and execute PHP.

Weakness: CWE-697 (Incorrect Comparison)

## Which versions are affected by CVE-2026-130675?


## How do I fix CVE-2026-130675?

No fix has been published for CVE-2026-130675 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-130675 being exploited?

There is no known exploitation of CVE-2026-130675 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130675 and fix it if it is affected.

What it is: CVE-2026-130675 is a critical vulnerability in craftcms cms, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130675 in the wild and no public exploit code.

Affected product: craftcms cms. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130675/ (Markdown: https://insights.sbomify.com/CVE-2026-130675/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130675
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130675
- OSV: https://osv.dev/vulnerability/CVE-2026-130675

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130675/
Summaries are generated and may contain mistakes; the official description above is the record.
