# CVE-2026-41172: Squidex vulnerable to Server-Side Request Forgery (SSRF) via URL-based asset upload (/api/apps/{app}/assets)

> An attacker with asset upload permissions can force the server to fetch arbitrary internal URLs, potentially exposing private network resources.

- **Severity:** High 7.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2026
- **Updated:** 23 Apr 2026
- **Also known as:** GHSA-x7cq-4f4c-8qcv

## What is CVE-2026-41172?

CVE-2026-41172 is a high-severity server-side request forgery vulnerability in squidex, published on 22 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Squidex is an open source headless content management system and content management hub. Prior to version 7.23.0, an SSRF vulnerability allows a user with asset upload permission to force the server to fetch arbitrary URLs, including localhost/private network targets, and persist the response as an asset. Version 7.23.0 contains a fix.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-41172 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41172 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41172 is a high-severity server-side request forgery vulnerability in squidex, published on 22 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41172 exists.

Affected product: squidex. 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-41172/ (Markdown: https://insights.sbomify.com/CVE-2026-41172/index.md)
```

## Sources

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

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