# CVE-2026-21433: Emlog vulnerable to Server-Side Request Forgery (SSRF)

> Attackers can trigger server-side requests via crafted SVG uploads in Emlog, enabling internal network probing and potential credential exposure.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **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:** 2 Jan 2026
- **Updated:** 5 Jan 2026
- **Also known as:** GHSA-6rwr-c8hc-mjj4

## What is CVE-2026-21433?

CVE-2026-21433 is a high-severity server-side request forgery vulnerability in Emlog Emlog, published on 2 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Emlog is an open source website building system. Versions up to and including 2.5.19 are vulnerable to server-side Out-of-Band (OOB) requests / SSRF via uploaded SVG files. An attacker can upload a crafted SVG to http[:]//emblog/admin/media[.]php which contains external resource references. When the server processes/renders the SVG (thumbnailing, preview, or sanitization), it issues an HTTP request to the attacker-controlled host. Impact: server-side SSRF/OOB leading to internal network probing and potential metadata/credential exposure. As of time of publication, no known patched versions are available.

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

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

It affects 1 product.


Products: Emlog Emlog.

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

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

## Is CVE-2026-21433 being exploited?

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

## Other vulnerabilities in Emlog Emlog

- [CVE-2025-29401](https://insights.sbomify.com/CVE-2025-29401/): File upload in n/a (critical 9.8)
- [CVE-2025-25783](https://insights.sbomify.com/CVE-2025-25783/): File upload in n/a (critical 9.8)
- [CVE-2023-44973](https://insights.sbomify.com/CVE-2023-44973/): File upload in n/a (critical 9.8)
- [CVE-2023-44974](https://insights.sbomify.com/CVE-2023-44974/): File upload in n/a (critical 9.8)
- [CVE-2023-43291](https://insights.sbomify.com/CVE-2023-43291/): Deserialization in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-21433 is a high-severity server-side request forgery vulnerability in Emlog Emlog, published on 2 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-21433 in the wild and no public exploit code.

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

## Sources

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

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