# CVE-2026-15378: Guardrails-detectors: guardrails-detectors: ssrf and local file read via user-supplied xml schema (xml-with-schema:)

> Remote attackers can exploit SSRF and local file read vulnerabilities in guardrails-detectors to access sensitive internal data and credentials.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-85xg-h6rv-rgf5

## What is CVE-2026-15378?

CVE-2026-15378 is a critical server-side request forgery vulnerability in Red Hat OpenShift AI 2.25, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in the `guardrails-detectors` component. This vulnerability allows a remote attacker to perform a blind Server-Side Request Forgery (SSRF) by submitting a specially crafted XML Schema Definition (XSD) string. This can lead to unauthorized access to sensitive information, including credentials from cloud metadata services, Kubernetes API, internal MinIO, and other internal network endpoints. Additionally, it enables local file reads of critical data such as service account tokens and pod secrets.

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

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


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

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

## Is CVE-2026-15378 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15378 is a critical server-side request forgery vulnerability in Red Hat OpenShift AI 2.25, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15378 in the wild and no public exploit code.

Affected product: Red Hat OpenShift AI 2.25. 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-15378/ (Markdown: https://insights.sbomify.com/CVE-2026-15378/index.md)
```

## Sources

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

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