CVE-2026-15143
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 · uneditedA flaw was found in the file_type content detector of guardrails-detectors. This vulnerability allows a remote attacker to supply an arbitrary XML Schema Definition (XSD) string, which is processed without proper restrictions. This can lead to server-side requests to arbitrary URLs or local file reads, potentially resulting in sensitive information disclosure, such as cloud provider credentials or access to internal network services.
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 · moderate confidenceThe file_type content detector in guardrails-detectors processes XML Schema Definition (XSD) strings without proper restrictions, allowing attackers to inject malicious XSD that triggers server-side requests to arbitrary URLs (SSRF) or reads local files. This enables sensitive information disclosure including cloud credentials and access to internal network services.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if guardrails-detectors package is installedRun 'pip show guardrails-detectors' or check your project's requirements.txt for the guardrails-detectors packageAffected if The package is present in the environment
-
Determine the installed version of guardrails-detectorsRun 'pip show guardrails-detectors' and note the Version field, then compare against any known affected version rangesAffected if The installed version falls within the affected version range (if known) or is an unpatched version
-
Verify if the file_type content detector is in useSearch your codebase for imports or usage of guardrails detectors that process file types, such as 'from guardrails_detectors import file_type' or similar patterns that invoke file type detectionAffected if The file_type detector is being called to process input content
-
Check if XSD content is being processed by the detectorInspect application logs, code, or request traces for XSD or XML Schema Definition content being passed to any detector functionAffected if XSD strings are being processed by the guardrails-detectors library
-
Inspect network traffic or logs for suspicious outbound connectionsReview application logs, network logs, or use a proxy to monitor outbound HTTP requests from the application server to unexpected or internal URLsAffected if The application is making unexpected requests to arbitrary URLs, which may indicate exploitation
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict input validation and disable external entity processing when parsing XSD content. Restrict the XML parser to prevent resolution of external entities and limit network access during schema processing.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15143 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15143 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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