# CVE-2026-100373: OpenMetadata through 2.0.2 SSRF via Webhook URL Validation Bypass

> Attackers with EventSubscription permissions can exploit SSRF to access internal networks and cloud metadata endpoints via webhook URL validation bypass.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-2qh3-cv3f-wh5h

## What is CVE-2026-100373?

CVE-2026-100373 is a medium-severity server-side request forgery vulnerability in open-metadata OpenMetadata, published on 25 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

OpenMetadata through 2.0.2 contains a server-side request forgery vulnerability in the URLValidator.validateURL function that fails to properly resolve DNS hostnames and validate internal addresses. Users permitted to create or update EventSubscription can set webhook destinations to internal hosts, allowing the server to send requests to private networks and cloud metadata endpoints while returning HTTP status codes that enable blind SSRF probing.

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

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


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

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

## Is CVE-2026-100373 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100373 is a medium-severity server-side request forgery vulnerability in open-metadata OpenMetadata, published on 25 Sep 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-100373 exists.

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

## Sources

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

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