# CVE-2026-42194: Incomplete fix for CVE-2026-32812: SSRF in admidio

> An incomplete SSRF fix in Admidio allows attackers to bypass IP validation via DNS rebinding, potentially accessing internal network resources.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 May 2026
- **Updated:** 7 May 2026
- **Also known as:** GHSA-hcjj-chvw-fmw9

## What is CVE-2026-42194?

CVE-2026-42194 is a medium-severity server-side request forgery vulnerability in admidio, published on 7 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Admidio is an open-source user management solution. Prior to version 5.0.9, the incomplete SSRF fix in Admidio's fetch_metadata.php validates the resolved IP address but passes the original hostname-based URL to curl_init(), leaving a DNS rebinding TOCTOU window that allows redirecting requests to internal IPs. This issue has been patched in version 5.0.9.

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

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

2 open source packages ship an affected version, including admidio/admidio.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `admidio/admidio` | Packagist | All versions | 5.0.9 |
| `admidio/admidio` | Packagist | All versions | 5.0.9 |

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

Upgrade admidio/admidio to 5.0.9 or later.

## Is CVE-2026-42194 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42194 is a medium-severity server-side request forgery vulnerability in admidio, published on 7 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42194 exists.

Affected packages and fixed versions:
- admidio/admidio (Packagist): affected all versions; fixed in 5.0.9
- admidio/admidio (Packagist): affected all versions; fixed in 5.0.9

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

## Sources

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

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