Vulnpedia
← All CVEs

CVE-2026-48710

MEDIUM 6.5 KNOWN EXPLOITED PoC CATALOGUED DETECTION TEMPLATE ALL-YEARS

Published 2026-05-26 · Last modified 2026-10-01 · GitHub_M · NVD: Analyzed

Starlette is a lightweight ASGI framework/toolkit. Prior to version 1.0.1, the HTTP `Host` request header was not validated before being used to reconstruct `request.url`. Because the routing algorithm relies on the raw HTTP path while `request.url` is rebuilt from the `Host` header, a malformed header could make `request.url.path` differ from the path that was actually requested. Middleware and endpoints that apply security restrictions based on `request.url` (rather than the raw `scope` path) could therefore be bypassed. Users should upgrade to a version greater than or equal to version 1.0.1, which validates the `Host` header against the grammar of RFC 9112 §3.2 / RFC 3986 §3.2.2 when constructing `request.url` and falls back to `scope["server"]` for malformed values.

ACTIVELY EXPLOITED

Confirmed exploited in the wild — in CISA KEV since 2026-09-02. Patch or mitigate now.

Exploitation likelihood

70.3%chance of exploitation in 30 days · 99th percentile

● In CISA KEV (2026-09-02)● Catalogued PoC◆ SSVC: exploitation active, automatable yes

Impact if exploited

6.5CVSS 3.1 · MEDIUM · CNA

  • ConfidentialityLow
  • IntegrityLow
  • AvailabilityNone

What an attacker needs

  • ✓Access: Reachable over the network — no local access needed
  • ✓Privileges: No account or privileges required
  • ✓User interaction: No user interaction needed
  • ✓Complexity: No special conditions — reliably repeatable

✓ lowers the bar for an attacker · ⚠ raises it

Proof of concept

Public PoC or exploit resources are catalogued below.

Listed by the named source; Vulnpedia has not tested these resources.

PoC data: JSON

Detection templates

Detection checks are listed separately from PoCs.

Resource commands

nuclei -id CVE-2026-48710 -u https://TARGETDetection template — review its checks and affected versions before use.
curl -s https://vulnpedia.com/cve/CVE-2026-48710/poc.jsonMachine-readable PoC index for this CVE (for automation).

Search for new PoCs

Search GitHub now — results may be empty or unverified.

Tracked sources are checked weekly for the full archive, including PoCs published after the original disclosure. A later release appears after a tracked source lists it and a refresh succeeds.

Data snapshot:

Affected

Vendors Kludex Red Hat Encode Redhat

Products Starlette Red Hat Ai Inference Server 3.3 Red Hat Ansible Automation Platform 2.6 Red Hat Ansible Automation Platform 2.7 Red Hat Migration Toolkit For Applications 8.2 Red Hat Openshift Ai 3.3 Red Hat Openshift Ai 3.4 Red Hat Satellite 6.17 Red Hat Satellite 6.18 Red Hat Satellite 6.19 Exploit Intelligence Openshift Lightspeed Red Hat Ai Inference Server Red Hat Ansible Automation Platform 2 Red Hat Enterprise Linux Ai (Rhel Ai) 3 Red Hat Openshift Ai (Rhoai) Ai Inference Server Ansible Automation Platform Migration Toolkit For Applications Openshift Ai Satellite Enterprise Linux Ai

Weakness (CWE)

  • CWE-444: : Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
  • CWE-1289: Improper Validation of Unsafe Equivalence in Input

CVSS vector

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

References and research data (JSON)

Packages and version ranges

Each advisory describes its own package and affected ranges. A boundary applies to that range; it is not a universal upgrade recommendation.

  • starlette PyPI

    pkg:pypi/starlette

    ECOSYSTEM range
    • All earlier versions (introduced 0)
    • Fixed boundary (excluded): 1.0.1
    191 explicitly listed affected versions

    0.1.0, 0.1.1, 0.1.10, 0.1.11, 0.1.12, 0.1.13, 0.1.14, 0.1.15, 0.1.16, 0.1.17, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.1.7, 0.1.8, 0.1.9, 0.10.0, 0.10.1, 0.10.2, 0.10.3, 0.10.4, 0.10.5, 0.10.6, 0.10.7, 0.11.0, 0.11.1, 0.11.2, 0.11.3, 0.11.4, 0.12.0, 0.12.0b1, 0.12.0b2, 0.12.0b3, 0.12.1, 0.12.10, 0.12.11, 0.12.12, 0.12.13, 0.12.2, 0.12.3, 0.12.4, 0.12.5, 0.12.6, 0.12.7, 0.12.8, 0.12.9, 0.13.0, 0.13.1, 0.13.2, 0.13.3, 0.13.4, 0.13.5, 0.13.6, 0.13.7, 0.13.8, 0.14.0, 0.14.1, 0.14.2, 0.15.0, 0.16.0, 0.17.0, 0.17.1, 0.18.0, 0.19.0, 0.19.1, 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.20.0, 0.20.1, 0.20.2, 0.20.3, 0.20.4, 0.21.0, 0.22.0, 0.23.0, 0.23.1, 0.24.0, 0.25.0, 0.26.0, 0.26.0.post1, 0.26.1, 0.27.0, 0.28.0, 0.29.0, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.3.5, 0.3.6, 0.3.7, 0.30.0, 0.31.0, 0.31.1, 0.32.0, 0.32.0.post1, 0.33.0, 0.34.0, 0.35.0, 0.35.1, 0.36.0, 0.36.1, 0.36.2, 0.36.3, 0.37.0, 0.37.1, 0.37.2, 0.38.0, 0.38.1, 0.38.2, 0.38.3, 0.38.4, 0.38.5, 0.38.6, 0.39.0, 0.39.1, 0.39.2, 0.4.0, 0.4.1, 0.4.2, 0.40.0, 0.41.0, 0.41.1, 0.41.2, 0.41.3, 0.42.0, 0.43.0, 0.44.0, 0.45.0, 0.45.1, 0.45.2, 0.45.3, 0.46.0, 0.46.1, 0.46.2, 0.47.0, 0.47.1, 0.47.2, 0.47.3, 0.48.0, 0.49.0, 0.49.1, 0.49.2, 0.49.3, 0.5.0, 0.5.1, 0.5.2, 0.5.3, 0.5.4, 0.5.5, 0.50.0, 0.51.0, 0.52.0, 0.52.1, 0.6.0, 0.6.1, 0.6.2, 0.6.3, 0.7.0, 0.7.1, 0.7.2, 0.7.3, 0.7.4, 0.8.0, 0.8.1, 0.8.2, 0.8.3, 0.8.4, 0.8.5, 0.8.6, 0.8.7, 0.8.8, 0.9.0, 0.9.1, 0.9.10, 0.9.11, 0.9.2, 0.9.3, 0.9.4, 0.9.5, 0.9.6, 0.9.7, 0.9.8, 0.9.9, 1.0.0, 1.0.0rc1

    Additional upstream package constraints
    {
  "database": {
    "last_known_affected_version_range": "<= 1.0.0",
    "source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/06/GHSA-86qp-5c8j-p5mr/GHSA-86qp-5c8j-p5mr.json"
  }
}
    GitHub Advisory Database · GHSA-86qp-5c8j-p5mr · Updated 2026-09-10T03:51:08.121685407Z
  • starlette PyPI

    pkg:pypi/starlette

    ECOSYSTEM range
    • All earlier versions (introduced 0)
    • Fixed boundary (excluded): 1.0.1
    191 explicitly listed affected versions

    0.1.0, 0.1.1, 0.1.10, 0.1.11, 0.1.12, 0.1.13, 0.1.14, 0.1.15, 0.1.16, 0.1.17, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.1.7, 0.1.8, 0.1.9, 0.10.0, 0.10.1, 0.10.2, 0.10.3, 0.10.4, 0.10.5, 0.10.6, 0.10.7, 0.11.0, 0.11.1, 0.11.2, 0.11.3, 0.11.4, 0.12.0, 0.12.0b1, 0.12.0b2, 0.12.0b3, 0.12.1, 0.12.10, 0.12.11, 0.12.12, 0.12.13, 0.12.2, 0.12.3, 0.12.4, 0.12.5, 0.12.6, 0.12.7, 0.12.8, 0.12.9, 0.13.0, 0.13.1, 0.13.2, 0.13.3, 0.13.4, 0.13.5, 0.13.6, 0.13.7, 0.13.8, 0.14.0, 0.14.1, 0.14.2, 0.15.0, 0.16.0, 0.17.0, 0.17.1, 0.18.0, 0.19.0, 0.19.1, 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.20.0, 0.20.1, 0.20.2, 0.20.3, 0.20.4, 0.21.0, 0.22.0, 0.23.0, 0.23.1, 0.24.0, 0.25.0, 0.26.0, 0.26.0.post1, 0.26.1, 0.27.0, 0.28.0, 0.29.0, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.3.5, 0.3.6, 0.3.7, 0.30.0, 0.31.0, 0.31.1, 0.32.0, 0.32.0.post1, 0.33.0, 0.34.0, 0.35.0, 0.35.1, 0.36.0, 0.36.1, 0.36.2, 0.36.3, 0.37.0, 0.37.1, 0.37.2, 0.38.0, 0.38.1, 0.38.2, 0.38.3, 0.38.4, 0.38.5, 0.38.6, 0.39.0, 0.39.1, 0.39.2, 0.4.0, 0.4.1, 0.4.2, 0.40.0, 0.41.0, 0.41.1, 0.41.2, 0.41.3, 0.42.0, 0.43.0, 0.44.0, 0.45.0, 0.45.1, 0.45.2, 0.45.3, 0.46.0, 0.46.1, 0.46.2, 0.47.0, 0.47.1, 0.47.2, 0.47.3, 0.48.0, 0.49.0, 0.49.1, 0.49.2, 0.49.3, 0.5.0, 0.5.1, 0.5.2, 0.5.3, 0.5.4, 0.5.5, 0.50.0, 0.51.0, 0.52.0, 0.52.1, 0.6.0, 0.6.1, 0.6.2, 0.6.3, 0.7.0, 0.7.1, 0.7.2, 0.7.3, 0.7.4, 0.8.0, 0.8.1, 0.8.2, 0.8.3, 0.8.4, 0.8.5, 0.8.6, 0.8.7, 0.8.8, 0.9.0, 0.9.1, 0.9.10, 0.9.11, 0.9.2, 0.9.3, 0.9.4, 0.9.5, 0.9.6, 0.9.7, 0.9.8, 0.9.9, 1.0.0, 1.0.0rc1

    Additional upstream package constraints
    {
  "database": {
    "source": "https://github.com/pypa/advisory-database/blob/main/vulns/starlette/PYSEC-2026-161.yaml"
  }
}
    PyPA · PYSEC-2026-161 · Updated 2026-05-26T15:41:31.112064345Z

Vendor product assessments

Showing 32 of 1847 vendor product statements; 1815 omitted. Read the full vendor advisory.

  • registry.redhat.io/rhaiis/vllm-cuda-rhel9@sha256:9165ca6c4f41ed4f5cdf5c590bfad74e22abe23737adfdc40a4c4b340b10e309_arm64 as a component of Red Hat AI Inference Server 3.3 · fixed

    Vendor assessment for this product only.

    pkg:oci/vllm-cuda-rhel9@sha256%3A9165ca6c4f41ed4f5cdf5c590bfad74e22abe23737adfdc40a4c4b340b10e309?arch=arm64&repository_url=registry.redhat.io/rhaiis/vllm-cuda-rhel9&tag=1782352847

    • vendor fix: For more information visit https://access.redhat.com/errata/RHSA-2026:30089 Vendor guidance
    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/rhaii/vllm-spyre-rhel9@sha256:8f3b2de1d5a8fdba70e937ff1ab95c0584cec32a4d58b1e636ea130a6461cea1_amd64 as a component of Red Hat AI Inference Server 3.4 · fixed

    Vendor assessment for this product only.

    pkg:oci/vllm-spyre-rhel9@sha256%3A8f3b2de1d5a8fdba70e937ff1ab95c0584cec32a4d58b1e636ea130a6461cea1?arch=amd64&repository_url=registry.redhat.io/rhaii/vllm-spyre-rhel9&tag=1789681201

    • vendor fix: For more information visit https://access.redhat.com/errata/RHSA-2026:69464 Vendor guidance
    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/rhelai3/bootc-gcp-cuda-rhel9@sha256:c1a193fa047eedbbf52be0b1d0f5d52e3e572d144a871f7c9322a34ba5abd92f_amd64 as a component of Red Hat Enterprise Linux AI 3.4 · fixed

    Vendor assessment for this product only.

    pkg:oci/bootc-gcp-cuda-rhel9@sha256%3Ac1a193fa047eedbbf52be0b1d0f5d52e3e572d144a871f7c9322a34ba5abd92f?arch=amd64&repository_url=registry.redhat.io/rhelai3/bootc-gcp-cuda-rhel9&tag=1790881123

    • vendor fix: The container images provided by this update can be downloaded from the Red Hat container registry at registry.redhat.io using the "podman pull" command. For details on deploying and configuring RHEL AI, see the Red Hat Enterprise Linux AI documentation at https://docs.redhat.com/en/documentation/red_hat_enterprise_linux_ai/3.4 Vendor guidance
    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/rhoai/odh-feature-server-rhel9@sha256:7c191c82302255ca50b047d803a20bdde14fc983e56d5c89c30fb16e0cbb7f69_amd64 as a component of Red Hat OpenShift AI 3.3 · fixed

    Vendor assessment for this product only.

    pkg:oci/odh-feature-server-rhel9@sha256%3A7c191c82302255ca50b047d803a20bdde14fc983e56d5c89c30fb16e0cbb7f69?arch=amd64&repository_url=registry.redhat.io/rhoai/odh-feature-server-rhel9&tag=1782997656

    • vendor fix: For Red Hat OpenShift AI 3.3.5 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/ Vendor guidance
    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/rhoai/odh-trustyai-garak-lls-provider-dsp-rhel9@sha256:5ccf83ca42677a3d86b182df4262fffaf2e5179886310593b04d015ad79d49eb_arm64 as a component of Red Hat OpenShift AI 3.3 · fixed

    Vendor assessment for this product only.

    pkg:oci/odh-trustyai-garak-lls-provider-dsp-rhel9@sha256%3A5ccf83ca42677a3d86b182df4262fffaf2e5179886310593b04d015ad79d49eb?arch=arm64&repository_url=registry.redhat.io/rhoai/odh-trustyai-garak-lls-provider-dsp-rhel9&tag=1790085310

    • vendor fix: For Red Hat OpenShift AI 3.3.7 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/ Vendor guidance
    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9@sha256:902bbeae50713b093e5e516a975c82241745c9f0b99051124120c503c38c919e_arm64 as a component of Red Hat OpenShift AI 3.3 · fixed

    Vendor assessment for this product only.

    pkg:oci/odh-workbench-jupyter-datascience-cpu-py312-rhel9@sha256%3A902bbeae50713b093e5e516a975c82241745c9f0b99051124120c503c38c919e?arch=arm64&repository_url=registry.redhat.io/rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9&tag=1782471661

    • vendor fix: For Red Hat OpenShift AI 3.3.5 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/ Vendor guidance
    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/rhoai/odh-feature-server-rhel9@sha256:c47f990eda9a49490c89d23f5e8ad0e9e394de95247d389c106d27b48a64240e_arm64 as a component of Red Hat OpenShift AI 3.4 · fixed

    Vendor assessment for this product only.

    pkg:oci/odh-feature-server-rhel9@sha256%3Ac47f990eda9a49490c89d23f5e8ad0e9e394de95247d389c106d27b48a64240e?arch=arm64&repository_url=registry.redhat.io/rhoai/odh-feature-server-rhel9&tag=1787068065

    • vendor fix: For Red Hat OpenShift AI 3.4.4 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/ Vendor guidance
    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9@sha256:f4dc82dead9aafc9f3c285e489fb04193105b864a518dee52c21a922693c94c8_s390x as a component of Red Hat OpenShift AI 3.4 · fixed

    Vendor assessment for this product only.

    pkg:oci/odh-pipeline-runtime-datascience-cpu-py312-rhel9@sha256%3Af4dc82dead9aafc9f3c285e489fb04193105b864a518dee52c21a922693c94c8?arch=s390x&repository_url=registry.redhat.io/rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9&tag=1782132686

    • vendor fix: For Red Hat OpenShift AI 3.4.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/ Vendor guidance
    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/rhoai/odh-trustyai-nemo-guardrails-server-rhel9@sha256:a796d1bb0bcd95acd9c66e185789d78e614ee8b53d9ef6efcbf4ba211c916a3a_ppc64le as a component of Red Hat OpenShift AI 3.4 · fixed

    Vendor assessment for this product only.

    pkg:oci/odh-trustyai-nemo-guardrails-server-rhel9@sha256%3Aa796d1bb0bcd95acd9c66e185789d78e614ee8b53d9ef6efcbf4ba211c916a3a?arch=ppc64le&repository_url=registry.redhat.io/rhoai/odh-trustyai-nemo-guardrails-server-rhel9&tag=1782420349

    • vendor fix: For Red Hat OpenShift AI 3.4.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/ Vendor guidance
    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9@sha256:803c490b945de2bd3168c134b4807f999adaeacfb4b134bce1c618bc2f5be9cd_arm64 as a component of Red Hat OpenShift AI 3.4 · fixed

    Vendor assessment for this product only.

    pkg:oci/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9@sha256%3A803c490b945de2bd3168c134b4807f999adaeacfb4b134bce1c618bc2f5be9cd?arch=arm64&repository_url=registry.redhat.io/rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9&tag=1782301637

    • vendor fix: For Red Hat OpenShift AI 3.4.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/ Vendor guidance
    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/satellite/iop-vulnerability-engine-rhel9@sha256:18805dc252fdc1c979e2324f61cc8e23b113b15c596a74d0efefd005aa85fbbc_amd64 as a component of Red Hat Satellite 6.19 · fixed

    Vendor assessment for this product only.

    pkg:oci/iop-vulnerability-engine-rhel9@sha256%3A18805dc252fdc1c979e2324f61cc8e23b113b15c596a74d0efefd005aa85fbbc?arch=amd64&repository_url=registry.redhat.io/satellite/iop-vulnerability-engine-rhel9&tag=1788190224

    • vendor fix: For Red Hat Lightspeed in Satellite installation see the Red Hat Satellite documentation. Vendor guidance
    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • openshift-lightspeed/lightspeed-service-api-rhel9 as a component of OpenShift Lightspeed · known affected

    Vendor assessment for this product only.

    pkg:oci/lightspeed-service-api-rhel9?repository_url=registry.redhat.io/openshift-lightspeed/lightspeed-service-api-rhel9

    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    • none available: Affected
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • rhaii/vllm-neuron-rhel9 as a component of Red Hat AI Inference Server · known affected

    Vendor assessment for this product only.

    pkg:oci/vllm-neuron-rhel9?repository_url=registry.redhat.io/rhaii/vllm-neuron-rhel9

    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    • no fix planned: Out of support scope
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • rhaiis/vllm-cpu-rhel9 as a component of Red Hat AI Inference Server · known affected

    Vendor assessment for this product only.

    pkg:oci/vllm-cpu-rhel9?repository_url=registry.redhat.io/rhaiis/vllm-cpu-rhel9

    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    • no fix planned: Will not fix
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • rhaiis/vllm-spyre-rhel9 as a component of Red Hat AI Inference Server · known affected

    Vendor assessment for this product only.

    pkg:oci/vllm-spyre-rhel9?repository_url=registry.redhat.io/rhaiis/vllm-spyre-rhel9

    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    • none available: Affected
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • ansible-automation-platform-25/lightspeed-chatbot-rhel8 as a component of Red Hat Ansible Automation Platform 2 · known affected

    Vendor assessment for this product only.

    pkg:oci/lightspeed-chatbot-rhel8?repository_url=registry.redhat.io/ansible-automation-platform-25/lightspeed-chatbot-rhel8

    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    • no fix planned: Out of support scope
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • rhelai3/bootc-rocm-rhel9 as a component of Red Hat Enterprise Linux AI (RHEL AI) 3 · known affected

    Vendor assessment for this product only.

    pkg:oci/bootc-rocm-rhel9?repository_url=registry.redhat.io/rhelai3/bootc-rocm-rhel9

    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    • none available: Affected
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • rhoai/odh-caikit-tgis-serving-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · known affected

    Vendor assessment for this product only.

    pkg:oci/odh-caikit-tgis-serving-rhel9?repository_url=registry.redhat.io/rhoai/odh-caikit-tgis-serving-rhel9

    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    • none available: Affected
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • rhoai/odh-llm-d-kv-cache-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · known affected

    Vendor assessment for this product only.

    pkg:oci/odh-llm-d-kv-cache-rhel9?repository_url=registry.redhat.io/rhoai/odh-llm-d-kv-cache-rhel9

    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    • none available: Affected
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • rhoai/odh-th06-cpu-torch210-py312-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · known affected

    Vendor assessment for this product only.

    pkg:oci/odh-th06-cpu-torch210-py312-rhel9?repository_url=registry.redhat.io/rhoai/odh-th06-cpu-torch210-py312-rhel9

    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    • none available: Affected
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • rhoai/odh-vllm-cuda-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · known affected

    Vendor assessment for this product only.

    pkg:oci/odh-vllm-cuda-rhel9?repository_url=registry.redhat.io/rhoai/odh-vllm-cuda-rhel9

    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    • none available: Affected
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • rhoai/odh-vllm-rocm-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · known affected

    Vendor assessment for this product only.

    pkg:oci/odh-vllm-rocm-rhel9?repository_url=registry.redhat.io/rhoai/odh-vllm-rocm-rhel9

    • workaround: Deploying an RFC-compliant reverse proxy (such as nginx, Apache, HAProxy, or Caddy) in front of the ASGI server will reject malformed Host headers before they reach the application. This is the most straightforward mitigation that does not require code changes. If custom middleware is present, it should be updated to use `request.scope["path"]` instead of `request.url.path` for any security decisions. The ASGI scope path is derived from the HTTP request line and is not influenced by the Host header, so it reflects the actual request target.
    • none available: Affected
    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/ansible-automation-platform-26/aap-must-gather-rhel9@sha256:3362761d6a5d99330d303adc87e1181369243147d56347362bfba62cc8047081_s390x as a component of Red Hat Ansible Automation Platform 2.6 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/aap-must-gather-rhel9@sha256%3A3362761d6a5d99330d303adc87e1181369243147d56347362bfba62cc8047081?arch=s390x&repository_url=registry.redhat.io/ansible-automation-platform-26/aap-must-gather-rhel9&tag=1779755048

    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/rhoai/odh-kserve-storage-initializer-rhel9@sha256:6c96958505eaac04880ffdc1ed29bace5f70836d7a14c91edb4dcbc51f762efb_ppc64le as a component of Red Hat OpenShift AI 2.25 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/odh-kserve-storage-initializer-rhel9@sha256%3A6c96958505eaac04880ffdc1ed29bace5f70836d7a14c91edb4dcbc51f762efb?arch=ppc64le&repository_url=registry.redhat.io/rhoai/odh-kserve-storage-initializer-rhel9&tag=1791257289

    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/rhoai/odh-data-science-pipelines-operator-controller-rhel9@sha256:f5cdd9a6edcc3638fed8ebf152f77964f145faadb8cb2556bfe5f8815a2573a2_arm64 as a component of Red Hat OpenShift AI 3.3 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/odh-data-science-pipelines-operator-controller-rhel9@sha256%3Af5cdd9a6edcc3638fed8ebf152f77964f145faadb8cb2556bfe5f8815a2573a2?arch=arm64&repository_url=registry.redhat.io/rhoai/odh-data-science-pipelines-operator-controller-rhel9&tag=1790133374

    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/rhoai/odh-model-metadata-collection-rhel9@sha256:053c9dbca6c20e761fce20802068e5ef7394a11bc73a06951a83f1f4f1fad200_amd64 as a component of Red Hat OpenShift AI 3.3 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/odh-model-metadata-collection-rhel9@sha256%3A053c9dbca6c20e761fce20802068e5ef7394a11bc73a06951a83f1f4f1fad200?arch=amd64&repository_url=registry.redhat.io/rhoai/odh-model-metadata-collection-rhel9&tag=1782471601

    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9@sha256:7c273bde8dc45b4c63669e8ae71f166fd084857f8474b589a7fba491c75d9087_amd64 as a component of Red Hat OpenShift AI 3.3 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/odh-workbench-jupyter-pytorch-cuda-py312-rhel9@sha256%3A7c273bde8dc45b4c63669e8ae71f166fd084857f8474b589a7fba491c75d9087?arch=amd64&repository_url=registry.redhat.io/rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9&tag=1789651387

    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/rhoai/odh-kserve-autogluon-server-rhel9@sha256:84ae9c3a4d291831994a8275add1b214cd1fb720424bc914a886c8455e170e15_arm64 as a component of Red Hat OpenShift AI 3.4 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/odh-kserve-autogluon-server-rhel9@sha256%3A84ae9c3a4d291831994a8275add1b214cd1fb720424bc914a886c8455e170e15?arch=arm64&repository_url=registry.redhat.io/rhoai/odh-kserve-autogluon-server-rhel9&tag=1782133320

    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/rhoai/odh-ml-pipelines-driver-rhel9@sha256:0f34024a0529d31771a82d5cbea690bd5eb2446435e66f8630abbb88b7c53334_ppc64le as a component of Red Hat OpenShift AI 3.4 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/odh-ml-pipelines-driver-rhel9@sha256%3A0f34024a0529d31771a82d5cbea690bd5eb2446435e66f8630abbb88b7c53334?arch=ppc64le&repository_url=registry.redhat.io/rhoai/odh-ml-pipelines-driver-rhel9&tag=1787333171

    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/rhoai/odh-model-performance-data-rhel9@sha256:935ac44fe155287dca76338be2d8cc77bf4ec9ffff60f441fa06e2b10cc6a7a9_arm64 as a component of Red Hat OpenShift AI 3.4 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/odh-model-performance-data-rhel9@sha256%3A935ac44fe155287dca76338be2d8cc77bf4ec9ffff60f441fa06e2b10cc6a7a9?arch=arm64&repository_url=registry.redhat.io/rhoai/odh-model-performance-data-rhel9&tag=1786611344

    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • registry.redhat.io/rhoai/odh-th06-cpu-torch210-py312-rhel9@sha256:cdd7d9f982c1f8a94dd4aad43e705274aae1bf0942e0442e60c3973f9c198f23_amd64 as a component of Red Hat OpenShift AI 3.4 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:oci/odh-th06-cpu-torch210-py312-rhel9@sha256%3Acdd7d9f982c1f8a94dd4aad43e705274aae1bf0942e0442e60c3973f9c198f23?arch=amd64&repository_url=registry.redhat.io/rhoai/odh-th06-cpu-torch210-py312-rhel9&tag=1787076778

    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00
  • rhoai/odh-mlserver-rhel9 as a component of Red Hat OpenShift AI (RHOAI) · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not in execute path

    pkg:oci/odh-mlserver-rhel9?repository_url=registry.redhat.io/rhoai/odh-mlserver-rhel9

    Red Hat · CVE-2026-48710 · Updated 2026-10-22T05:13:44+00:00

Unverified PoC candidates

Catalogue matches for further research. These repositories have not been validated as working exploits.

5 candidates

Additional exploitation reports

Source-specific reports, separate from CISA KEV. Repeated observations from one source are not independent confirmations.

  • VulnCheck KEV · 2026-05-26T00:00:00Z

    Source guidance: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

    Source ransomware assessment: Known

    VulnCheck KEV · CVE-2026-48710 · Updated 2026-05-26T00:00:00Z
  • VulnCheck KEV · 2026-05-26T00:00:00ZVulnCheck KEV · CVE-2026-48710
  • VulnCheck KEV · 2026-08-26T00:00:00ZVulnCheck KEV · CVE-2026-48710
  • VulnCheck KEV · 2026-08-27T00:00:00ZVulnCheck KEV · CVE-2026-48710
  • VulnCheck KEV · 2026-09-02T00:00:00ZVulnCheck KEV · CVE-2026-48710
    VulnCheck KEV · CVE-2026-48710

Known Affected Software Configurations

VendorProductVersion range
EncodeStarlette≥ 0.8.3 and < 1.0.1
RedhatAi Inference Server≥ 3.3.0 and ≤ 3.3.5
RedhatAnsible Automation Platform2.6
RedhatAnsible Automation Platform2.7
RedhatMigration Toolkit For Applications< 8.2.0
RedhatOpenshift Ai≥ 3.3 and < 3.3.5
RedhatOpenshift Ai≥ 3.4 and < 3.4.2
RedhatOpenshift Lightspeed*
RedhatSatellite6.17
RedhatSatellite6.18
RedhatSatellite6.19
RedhatEnterprise Linux Ai3.0

All CVSS metrics

  • MEDIUM 6.5 v3.1 · CNA Primary
    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
  • MEDIUM 6.5 v3.1 · ADP Primary
    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
  • MEDIUM 6.5 v3.1 · NVD Secondary
    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

References

Exploit-tagged references (not proof of a PoC)

Patches & mitigations

Advisories

Technical & other

Sources: NVD · CVE.org · All sources and attribution · EPSS