dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-15378

CRITICAL · 9.3 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A blind Server-Side Request Forgery (SSRF) vulnerability in the guardrails-detectors component allows remote attackers to submit specially crafted XML Schema Definition (XSD) strings that cause the server to make unauthorized requests to internal services (cloud metadata endpoints, Kubernetes API, MinIO) and read local files including service account tokens and pod secrets.

MitigationImplement strict input validation on XSD processing to block or sanitize potentially dangerous constructs, and enforce network isolation by restricting outbound connections from the processing component to prevent unauthorized internal network access and file system operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify guardrails-detectors installation
    Search for the guardrails-detectors package or module in your application dependencies, container images, or installed software listings. Check package managers, container manifests, or dependency files (e.g., requirements.txt, package.json, Dockerfile) for this component.
    Affected if The guardrails-detectors component is present in your environment
  2. Locate XSD processing configuration
    Search configuration files, application settings, and code repositories for XSD validation, XML schema processing, or XML parsing functionality tied to the guardrails-detectors component. Look for settings named xsd, schema validation, or xml processing.
    Affected if XSD processing or XML schema validation is enabled or configured for guardrails-detectors
  3. Verify network egress rules
    Review firewall rules, network policies, and security group configurations to determine if the guardrails-detectors component can initiate outbound HTTP/HTTPS connections to internal IP ranges (169.254.169.254 for cloud metadata), Kubernetes API servers, or MinIO endpoints.
    Affected if Outbound network access from the processing component is permitted to internal services or metadata endpoints
  4. Check for sensitive file access
    Audit file system permissions and access logs to see if the guardrails-detectors process has read access to /var/run/secrets/, service account token paths, pod metadata directories, or other sensitive local files.
    Affected if The component has read access to Kubernetes service account tokens, pod secrets, or other sensitive local files
  5. Review XSD input handling
    Examine how XSD strings are submitted to the guardrails-detectors component. Check if there is an API endpoint, function, or input field that accepts raw XSD content without strict validation or sanitization.
    Affected if User-supplied XSD content is accepted directly without strict input validation

Your environment is affected if the guardrails-detectors component with XSD processing is installed and accepts external XSD input without strict validation, and the component has network access to internal services or file system access to sensitive paths.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on XSD processing to block or sanitize potentially dangerous constructs, and enforce network isolation by restricting outbound connections from the processing component to prevent unauthorized internal network access and file system operations.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15378 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15378 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data