RHSA-2026:86891CriticalCVSS 9.8

Red Hat Security Advisory: RHOAI 3.5.2 - Red Hat OpenShift AI

Published
October 21, 2026
Last Modified
October 26, 2026

🔗 CVE IDs covered (93)

CVE-2026-84375 →CVE-2026-91990 →CVE-2026-104852 →CVE-2026-76169 →CVE-2026-84382 →CVE-2026-102938 →CVE-2026-104873 →CVE-2026-56859 →CVE-2026-75975 →CVE-2026-76905 →CVE-2026-85124 →CVE-2026-87817 →CVE-2026-88031 →CVE-2026-66007 →CVE-2026-73646 →CVE-2026-78679 →CVE-2026-84394 →CVE-2026-84428 →CVE-2026-96749 →CVE-2026-54284 →CVE-2026-62243 →CVE-2026-76222 →CVE-2026-81725 →CVE-2026-88029 →CVE-2026-104861 →CVE-2026-49825 →CVE-2026-69112 →CVE-2026-71281 →CVE-2026-81727 →CVE-2026-84292 →CVE-2026-13697 →CVE-2026-15679 →CVE-2026-73417 →CVE-2026-76098 →CVE-2026-84381 →CVE-2026-85525 →CVE-2026-96775 →CVE-2026-102925 →CVE-2026-19534 →CVE-2026-63374 →CVE-2026-77874 →CVE-2026-81724 →CVE-2026-81726 →CVE-2026-84445 →CVE-2026-93657 →CVE-2026-104851 →CVE-2026-79675 →CVE-2026-81722 →CVE-2026-84469 →CVE-2026-86332 →CVE-2026-93749 →CVE-2026-102990 →CVE-2026-63209 →CVE-2026-68494 →CVE-2026-69097 →CVE-2026-69243 →CVE-2026-73508 →CVE-2026-78676 →CVE-2026-87819 →CVE-2026-89425 →CVE-2026-62384 →CVE-2026-69244 →CVE-2026-78677 →CVE-2026-59296 →CVE-2026-69152 →CVE-2026-71491 →CVE-2026-73502 →CVE-2026-84504 →CVE-2026-84961 →CVE-2026-93599 →CVE-2024-14029 →CVE-2026-18427 →CVE-2026-49855 →CVE-2026-68497 →CVE-2026-79674 →CVE-2026-80205 →CVE-2026-15789 →CVE-2026-59893 →CVE-2026-75931 →CVE-2026-82417 →CVE-2026-84782 →CVE-2026-85152 →CVE-2026-87776 →CVE-2026-75838 →CVE-2026-78682 →CVE-2026-82397 →CVE-2026-93348 →CVE-2026-102930 →CVE-2026-102937 →CVE-2026-37237 →CVE-2026-75899 →CVE-2026-76172 →CVE-2026-77354 →

📋 Description

CVE-2024-14029 — python-tornado: Tornado before 6.4.1 HTTP Request Smuggling via Transfer-Encoding CVE-2026-13697 — undici: undici: Information disclosure and Denial of Service via malformed Cache-Control directives CVE-2026-15679 — timm: Hugging Face PyTorch Image Models: Remote Code Execution via Deserialization of Untrusted Data CVE-2026-15789 — buildkit: github.com/moby/buildkit: BuildKit: File escape vulnerability CVE-2026-18427 — @fastify/static: @fastify/static: Information disclosure via route guard bypass CVE-2026-19534 — undici: undici: Denial of Service via unrequested WebSocket subprotocol CVE-2026-37237 — vllm: vLLM: Denial of Service via memory exhaustion from oversized media files CVE-2026-49825 — lxml: lxml-html-clean: lxml: URL bypass vulnerability in Cleaner via missing xlink:href CVE-2026-49855 — tornado: Tornado: Denial of Service via uncontrolled gzip decompression memory consumption CVE-2026-54284 — sqlparse: sqlparse: Denial of Service via quadratic CPU consumption in SQL parsing CVE-2026-56859 — encoding/xml: golang: Go: Denial of Service via XML decoding recursion depth issue CVE-2026-59296 — io.micrometer/micrometer-registry-statsd: io.micrometer/micrometer-core: Micrometer: Line-protocol and log injection via unsanitized input allows metric and log spoofing CVE-2026-59893 — sqlparse: sqlparse: Denial of Service via inefficient SQL parsing CVE-2026-62243 — io.netty/netty-handler: Netty: TLS hostname verification bypass via OpenSSL client path misconfiguration CVE-2026-62384 — nltk: NLTK: Information Disclosure via Symlink Sandbox Bypass CVE-2026-63209 — github.com/klauspost/compress: klauspost/compress: Denial of Service via integer overflow in dictionary processing CVE-2026-63374 — anyio: AnyIO: TLS certificate spoofing via improper internationalized domain name encoding CVE-2026-66007 — datasets: Datasets: Information disclosure via path traversal vulnerability CVE-2026-68494 — com.fasterxml.jackson.core/jackson-core: tools.jackson.core/jackson-core: jackson-core: Denial of Service via incomplete fix in async JSON parser CVE-2026-68497 — com.fasterxml.jackson.core/jackson-databind: tools.jackson.core/jackson-databind: jackson-databind: CPU Denial of Service via unbounded numeric parsing CVE-2026-69097 — gitpython: GitPython: Remote Code Execution via Config Injection in Submodule Names CVE-2026-69112 — accelerate: Hugging Face Accelerate: Path Traversal and Denial of Service via weight_map CVE-2026-69152 — brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation CVE-2026-69243 — aiohttp: AIOHTTP: HTTP Request Smuggling via WebSocket Upgrade CVE-2026-69244 — aiohttp: AIOHTTP: Denial of Service via malformed HTTP responses CVE-2026-71281 — peft: peft: Arbitrary Code Execution via Unsafe Deserialization in LoRA-GA and CorDA Modules CVE-2026-71491 — sqlparse: sqlparse: Denial of Service via quadratic CPU consumption in comment grouping CVE-2026-73417 — jupyterlab: JupyterLab: Cross-site scripting (XSS) allows arbitrary code execution CVE-2026-73502 — github.com/getkin/kin-openapi: kin-openapi: Denial of Service via unauthenticated nil-pointer dereference CVE-2026-73508 — io.netty/netty-codec-dns: Netty: Denial of Service via Memory Leak in DNS Record Decoder with Malformed Domain Names CVE-2026-73646 — postcss: PostCSS: Information disclosure via path traversal in source map auto-loading CVE-2026-75838 — dompurify: DOMPurify: Cross-Site Scripting via IN_PLACE sanitization CVE-2026-75899 — fast-uri: fast-uri: Server-Side Request Forgery via repeated hostname percent-decoding CVE-2026-75931 — fast-uri: fast-uri: Host confusion via skipped IDN canonicalization CVE-2026-75975 — fast-uri: fast-uri: Server-side request forgery via malformed IPv6 normalization CVE-2026-76098 — mistune: Mistune: Denial of Service via excessive emphasis markers in Markdown CVE-2026-76169 — fastify: fastify: Authentication bypass via malformed URLs CVE-2026-76172 — fast-uri: fast-uri: URI parsing flaw enables server-side request forgery and redirects CVE-2026-76222 — gitpython: GitPython: Arbitrary file creation via path traversal in .gitmodules submodule names CVE-2026-76905 — github.com/getkin/kin-openapi: kin-openapi: Denial of Service via malformed multipart/form-data body CVE-2026-77354 — github.com/getkin/kin-openapi: kin-openapi: Denial of Service via uncontrolled resource consumption in deepObject query parameter decoding CVE-2026-77874 — org.hibernate/hibernate-core: Hibernate ORM: SQL Injection via unescaped JSON path segment allows data exfiltration and authorization bypass CVE-2026-78676 — gitpython: GitPython before 3.1.59 Remote Code Execution via Config Injection CVE-2026-78677 — GitPython: GitPython: Arbitrary Code Execution via Path Traversal CVE-2026-78679 — GitPython: GitPython: Arbitrary file read via TagReference.create() CVE-2026-78682 — nltk: NLTK: Server-Side Request Forgery via HTTP Proxy Configuration CVE-2026-79674 — nltk: NLTK: Information disclosure via path traversal in corpus-reader constructors CVE-2026-79675 — nltk: NLTK before 3.10.3 JVM Argument Injection via Per-Call Options CVE-2026-80205 — nltk: NLTK: Denial of Service via unvalidated regular expressions CVE-2026-81722 — nltk: nltk PorterStemmer: Denial of Service due to inefficient token processing CVE-2026-81724 — nltk: NLTK: Denial of Service via Uncontrolled Recursion CVE-2026-81725 — nltk: NLTK: Regular Expression Denial of Service via malformed TEI blocks CVE-2026-81726 — nltk: NLTK: Unauthorized file access via path traversal in model-artifact APIs CVE-2026-81727 — nltk: NLTK: Filesystem containment bypass allows local file overwrite CVE-2026-82397 — python-tornado: Tornado: Denial of Service via excessive URL-encoded body fields CVE-2026-82417 — qs: qs: Denial of Service via improper validation in stringify function CVE-2026-84292 — fast-uri: fast-uri: Authority Injection via Unvalidated Port Serialization CVE-2026-84375 — js-yaml: js-yaml: Denial of Service vulnerability in YAML parsing CVE-2026-84381 — httpx2: httpcore2: HTTPX2: WebSocket traffic sent in plaintext via SOCKS5 proxy due to TLS failure CVE-2026-84382 — httpx2: HTTPX2: Denial of Service via streaming response decompression memory amplification CVE-2026-84394 — fast-uri: fast-uri: Host confusion via unbalanced URI brackets can bypass security policies CVE-2026-84428 — fastify: fastify: Header validation bypass via incomplete schema case normalization CVE-2026-84445 — google.golang.org/grpc: gRPC-Go: Denial of Service via malformed RPC requests CVE-2026-84469 — fastify: Fastify: Request validation bypass allows unauthorized operations CVE-2026-84504 — fastify: fastify: Unauthorized state changes and data disclosure via request body replacement CVE-2026-84782 — openssl: compat-openssl: openssl: Information disclosure via DTLS handshake retransmission CVE-2026-84961 — undici: undici: TLS certificate validation bypass in BalancedPool via dropped connect options CVE-2026-85124 — @fastify/http-proxy: @fastify/http-proxy: Information disclosure via path traversal with backslash dot-segments CVE-2026-85152 — undici: undici: Authentication bypass via cross-origin cache poisoning due to missing origin isolation CVE-2026-85525 — snowflake-connector-python: github.com/snowflakedb/snowflake-go: snowflake-sdk: net.snowflake/snowflake-jdbc: Snowflake Drivers: Data interception via improper OCSP response validation CVE-2026-86332 — odh-dashboard: odh-dashboard: NIM credential Secret readable by any authenticated user CVE-2026-87776 — compression: compression: Denial of Service via memory leak on premature response close CVE-2026-87817 — GitPython: GitPython: Remote Code Execution via Git directory impersonation CVE-2026-87819 — GitPython: GitPython: Denial of Service via crafted commit author field CVE-2026-88029 — pymongo: MongoDB Python Driver: Data disclosure and denial of service via query-operator injection CVE-2026-88031 — go.mongodb.org/mongo-driver: go.mongodb.org/mongo-driver/v2: MongoDB Go Driver: Data deletion via query-operator injection in GridFS file IDs CVE-2026-89425 — com.fasterxml.jackson.core/jackson-core: Jackson-core: Denial of Service via unbounded StringBuilder growth during malformed token processing CVE-2026-91990 — tornado: Tornado: Denial of Service via memory amplification in multipart parsing CVE-2026-93348 — unsloth-zoo: unsloth: Unsloth Zoo: Arbitrary code execution via crafted model configuration CVE-2026-93599 — rustls-webpki: rustls-webpki: Denial of Service via crafted Certificate Revocation List CVE-2026-93657 — hickory-resolver: hickory-resolver: DNSSEC validation bypass allows forged DNS records CVE-2026-93749 — source-map-js: source-map-js: Denial of Service via malformed indexed source maps CVE-2026-96749 — pymongo: pymongo: Out-of-bounds write via integer overflow during BSON encoding CVE-2026-96775 — mlflow: MLflow dspy: Arbitrary code execution via crafted MLmodel artifact CVE-2026-102925 — virtualenv: virtualenv: Arbitrary code execution via crafted paths in activation scripts CVE-2026-102930 — virtualenv: virtualenv: Arbitrary code execution via unverified downloaded seed wheels CVE-2026-102937 — virtualenv: virtualenv: Arbitrary code execution via unescaped prompt in Windows activation script CVE-2026-102938 — virtualenv: virtualenv: Arbitrary code execution via configuration injection in prompt values CVE-2026-102990 — basic-ftp: basic-ftp: Denial of Service via crafted Unix directory listings CVE-2026-104851 — fsspec: fsspec: arbitrary code execution via unrestricted template rendering in ReferenceFileSystem CVE-2026-104852 — @graphql-tools/utils: @graphql-tools/utils: Denial of Service (DoS) via prototype pollution in mergeDeep CVE-2026-104861 — probe-image-size: probe-image-size: Denial of Service via crafted SVG input CVE-2026-104873 — langgraph-sdk: langgraph-sdk: Authorization bypass via improper resource handler registration

🎯 Affected products200

  • Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-ai-gateway-operator-rhel9@sha256:3f59cdb3c2978ec98973d54226b23e3f106a872d25eab72590f834b7da2994af_s390x as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-ai-gateway-operator-rhel9@sha256:42e9ee87f4822181d55400436978a1bad13e2d311f3a7b7de701798cf39c5b83_ppc64le as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-ai-gateway-operator-rhel9@sha256:69e7eb84b46520c787d7458620734a857b0202c12c0ea3b29f1fd1e21bf56cab_arm64 as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-ai-gateway-operator-rhel9@sha256:7c11a4e55823f20428781b68e8bf5f4e9f86c70c18f45893859b354a1292052e_amd64 as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-ai-gateway-payload-processing-rhel9@sha256:1bcc29048c115be809a133889b6fc70f6f413b72620466af1f3904b05aab8d24_arm64 as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-ai-gateway-payload-processing-rhel9@sha256:585ff0f0eaf0ca053a704d23e809380ea7fb2a69ca07b1c60bf41141029efbb7_amd64 as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-ai-gateway-payload-processing-rhel9@sha256:d42c1fdf09bfe9e977dbed7b0e4ec29f7af08e9d78ab10f136ffbafb31401abb_ppc64le as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-ai-gateway-payload-processing-rhel9@sha256:d5e115c3becbfb7bd88c004edee894efddf4b5a5006903a27bff082554a90266_s390x as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-automl-rhel9@sha256:692f4f1fe815ff4403a351fb60943000fde59c54af98a53d46e6f6bb93b04d24_ppc64le as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-automl-rhel9@sha256:997c3f85db870ee35193516607f600d5ed5481a6daf78fe85dcfc4399b191d1a_s390x as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-automl-rhel9@sha256:a6370c8e2f7e99d23fa9c4465136839c7adeff8e2188271f24a73b84e65df635_amd64 as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-automl-rhel9@sha256:b23f78d55cfda4b76aad70c8a2e5725ce59d4f9f77684f201d4a059ffb7d3a77_arm64 as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-autorag-rhel9@sha256:3df9d7f166b9beffdfeb0239594e1f8e53a3108047f5e649bc004ba95b5a0628_s390x as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-autorag-rhel9@sha256:45c7b27fcac23c644784a8053b70d8c1b3ec255081a707cb74e70bf7e034c68d_arm64 as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-autorag-rhel9@sha256:4a414f71cd3f25bb9203c6bfc5e0adc037453090a290a277417d53ca5b6ab325_ppc64le as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-autorag-rhel9@sha256:67858a9659470be792d2d47b9cb5ae942d02c6c97b2b53eb03a992f303f26441_amd64 as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-built-in-detector-rhel9@sha256:101fd6a0f9c4aac4f5d2ca30d9a716728b27e2de6523e8ae6a965c8f3d1f4632_ppc64le as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-built-in-detector-rhel9@sha256:1b9cc7861bc46b4578f08eccaab0781282681f93203956903658b5c84418f52f_arm64 as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-built-in-detector-rhel9@sha256:bfc458a0c63c8d9e4c43f28833f248644ffc1af588cc0580ecf818e762240310_amd64 as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-built-in-detector-rhel9@sha256:e9915a64e251d3bf4bcdb222278f8b3413e2ec72b9657cc86c31a99254903bc7_s390x as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-cli-rhel9@sha256:7063100cab54fb0662809c17daa09e7ee74316eebcb4699d7ea870e09d4a30ad_amd64 as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-cli-rhel9@sha256:8fbcd14329f9644a11f77484853ef68d7fca7667f840feb4726a433a33d7dcb8_arm64 as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-core-bff-rhel9@sha256:0667659ceec2c73a63b75e9691ca880a33861eb7a3f6665e5a06d19ef5e37ecd_s390x as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-core-bff-rhel9@sha256:19e565c46846889b53b96b7160d908c9dff2fd21ab75f1939f4dbae85ba51624_arm64 as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-core-bff-rhel9@sha256:85e1658741d973002527ff0bfa482740facb4a32d3b46cbf90e2070db28a8431_ppc64le as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-core-bff-rhel9@sha256:de9f7a1bbf0734f894843e0c7955ba0d3f35334d3afee9229102e0b02ad663ef_amd64 as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-dashboard-operator-rhel9@sha256:1661963772f166263e4a71703ced1fee5569ce4faa480af0d469e32abd0217fd_s390x as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-dashboard-operator-rhel9@sha256:78d486dd6ae359e0f0cd7e8cb20a42f1e19f73c5b57d58f433089ce1d80bf4dd_arm64 as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhoai/odh-dashboard-operator-rhel9@sha256:d0ff5e12c326f1c8bf6b7fa8ac501871ffe346c14cd35160fde4572137a25b8c_amd64 as a component of Red Hat OpenShift AI 3.5
  • +170 more not shown

✅ Remediation

For Red Hat OpenShift AI 3.5.2 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this errata update: https://docs.redhat.com/en/documentation/red_hat_openshift_ai/ Workaround: Configure upstream reverse proxies or load balancers to strictly normalize HTTP headers and reject any incoming requests containing duplicate Transfer-Encoding headers before they reach the backend Tornado application worker. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: Restricting the domains that vLLM is allowed to fetch media from reduces exposure to this issue. Set the `--allowed-media-domains` option to an explicit allowlist of the domains you expect media to come from (for example `--allowed-media-domains upload.wikimedia.org github.com`), so that clients cannot direct the server to download arbitrarily large files from arbitrary hosts. Also consider setting `VLLM_MEDIA_URL_ALLOW_REDIRECTS=0` so that HTTP redirects cannot be followed to bypass the domain restrictions, as recommended in the upstream vLLM security documentation. Note that this restricts which hosts may be fetched but does not by itself impose a limit on the size of responses served by allowlisted domains. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. The upstream project addressed this issue in sqlparse 0.6.0, and Red Hat products that bundle sqlparse will receive remediation through their respective update streams as fixes become available. Workaround: This vulnerability only affects applications that explicitly configure Netty to use the OpenSSL TLS provider (SslProvider.OPENSSL). The following mitigations can reduce exposure without applying a patch: 1) Use the default JDK SSL provider — Do not configure SslProvider.OPENSSL in your Netty SslContext setup. The default JDK SSL provider (SslProvider.JDK) is not affected by this vulnerability. Most applications use the JDK default unless explicitly overridden. 2) Use X509ExtendedTrustManager — If the OpenSSL provider is required, ensure the configured trust manager extends X509ExtendedTrustManager rather than the plain X509TrustManager interface. The extended variant performs hostname verification independently of the Netty wrapping logic. 3) Run on Java 24 or earlier — The vulnerable code path only triggers on Java 25+ where sun.misc.Unsafe-based trust-manager wrapping is unavailable. Running on earlier Java versions (e.g., Java 21 LTS) means the wrapping works correctly and hostname verification stays enabled. Workaround: Restrict write permissions on NLTK corpus subdirectories to prevent unauthorized symlink creation, or sanitize input paths to prevent FramenetCorpusReader from loading untrusted corpus files containing unresolved symbolic links. Workaround: To mitigate this issue, ensure that all `file_name` metadata processed by the `datasets` library, especially within folder-based dataset builders, is thoroughly validated and sanitized. Avoid processing `file_name` values from untrusted sources without strict input validation to prevent directory traversal sequences. This will prevent the embedding of arbitrary local files during `save_to_disk` or `push_to_hub` operations. Workaround: Upgrade com.fasterxml.jackson.core:jackson-core to a fixed version, such as 2.18.8 or later, 2.21.4 or later, or the first fixed release in the applicable 2.22.x stream. For Jackson 3.x, upgrade to 3.1.4 or later, or the first fixed release in the applicable 3.2.x stream. If upgrading is not immediately possible, do not expose the non-blocking parser to untrusted, incrementally streamed JSON. Where feasible, use a synchronous parser or buffer and enforce strict request-size, connection-timeout, and concurrency limits at the ingress layer. Apply the upgrade as soon as possible because ingress limits reduce exposure but do not correct the parser defect. Workaround: Upgrade jackson-databind to 2.18.10, 2.21.6, 2.22.2, or later fixed releases as applicable. Until updated, restrict untrusted JSON input size and complexity. Workaround: To mitigate this issue, users should avoid cloning or creating submodules from untrusted Git repositories. Exercise caution when interacting with Git repositories from unknown or unverified sources, as processing malicious submodule names can lead to configuration injection and potential remote code execution. Always ensure the integrity and trustworthiness of Git repositories before performing operations that involve submodule creation or cloning. Workaround: To mitigate this vulnerability, do not pass untrusted input to the expand() function. Workaround: Do not load LoRA-GA or CorDA cache/covariance files from untrusted or unverified sources; only use cache files generated in your own trusted training environment. Upgrade to a peft release newer than 0.19.1 once available in the affected image. Workaround: Users should avoid importing `overrides.json` files from untrusted sources. Additionally, ensure that shared settings locations are secured to prevent unauthorized modification by attackers. Workaround: As a partial workaround, administrators can audit their OpenAPI specification files and ensure every content parameter declares an explicit schema for each media type, which prevents the nil-dereference code path from being reached. Workaround: Red Hat recommends upgrading to a fixed version as the primary remediation. Where an immediate upgrade is not possible, restrict network access so that only trusted DNS servers and trusted network peers can send DNS traffic to the affected application, using firewall or network policy rules to block or rate-limit DNS traffic from untrusted sources. This reduces exposure to the malformed DNS records that trigger the issue but does not fully eliminate it; upgrading remains the only complete fix. Workaround: To mitigate this vulnerability, avoid using DOMPurify with a custom IN_PLACE sanitization configuration that includes an element-removal hook. Default DOMPurify configurations are not affected by this flaw. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Until updates are available, restrict the processing of user-supplied URIs to trusted sources only, implement strict allowlists for destination hosts (preferably IP-based rather than hostname-based), and apply egress filtering to prevent server-initiated connections to internal networks or cloud metadata services. Workaround: Mitigation for this issue involves restricting the processing of untrusted Markdown content by applications utilizing the vulnerable Mistune library. If applications are exposed to untrusted input, implement input sanitization to prevent deeply nested emphasis structures that could trigger the denial of service. Workaround: There is no mitigation available for this issue. Apply updates as they become available from Red Hat product teams. Workaround: There is no mitigation beyond not cloning or initializing git submodules from untrusted repositories. Upgrade to GitPython 3.1.58 or later when it becomes available. Workaround: To mitigate this vulnerability, applications using Hibernate ORM should avoid passing untrusted user-controlled input directly as JSON path arguments to `json_query`, `json_exists`, or `json_value` functions. If dynamic JSON querying is necessary, strictly validate or whit…

🔗 References (97)