dbcve.org
Openshift AiApplication · Redhat

CVE-2026-15154

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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 `guardrails-detectors`, a component of Red Hat OpenShift AI. This vulnerability, known as Regular Expression Denial of Service (ReDoS), allows a remote attacker to provide specially crafted regular expressions to the public detection API. This can cause catastrophic backtracking, leading to a worker process consuming 100% CPU indefinitely and resulting in a denial of service for the entire guardrails-mediated LLM pipeline.

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 confidence

A ReDoS vulnerability in guardrails-detectors allows remote attackers to submit specially crafted regular expressions to the public detection API, triggering catastrophic backtracking that causes the worker process to consume 100% CPU indefinitely, resulting in denial of service for the entire guardrails-mediated LLM pipeline.

MitigationImplement input validation to reject or limit regex complexity, add execution timeouts for regex operations, and sanitize user-provided regex patterns before processing.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openshift AiApplication
Affected:all versions

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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 deployment
    Check if guardrails-detectors is deployed in the OpenShift AI environment by running 'oc get deployments -A | grep guardrails' or inspecting the OpenShift AI operator managed components
    Affected if guardrails-detectors component is present and running in the namespace
  2. Locate the public detection API endpoint
    Review OpenShift AI service routes and ingress configurations to identify endpoints that accept regex input for detection purposes, typically under the /api/guardrails or /detect paths
    Affected if a public-facing detection API endpoint that accepts regex patterns is exposed
  3. Verify input validation configuration
    Examine guardrails-detectors configuration files and deployment specs for any regex complexity limits, pattern validation rules, or input sanitization settings (look for fields like max_pattern_length, allowed_characters, or validation_enabled)
    Affected if no input validation, length limits, or complexity restrictions are configured for regex submissions to the detection API
  4. Check for regex execution timeouts
    Inspect the guardrails-detectors deployment environment variables and configuration for timeout settings on regex operations (search for TIMEOUT, MAX_EXECUTION_TIME, or similar timeout-related parameters)
    Affected if no timeout or indefinite execution time is configured for regex pattern matching operations
  5. Confirm API accessibility from external networks
    Test whether the detection API endpoint is reachable from outside the cluster by attempting a curl request to the exposed route or checking network policies that allow external access
    Affected if the detection API accepts requests from untrusted or external network sources without authentication or rate limiting

The environment is affected if guardrails-detectors is deployed with an exposed public detection API that accepts regex input without validation, length limits, or execution timeouts.

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 input validation to reject or limit regex complexity, add execution timeouts for regex operations, and sanitize user-provided regex patterns before processing.

Fix this in Openshift Ai Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15154 — 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-15154 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