Skip to main content
CVE-2026-48710VulnerabilityPublished Updated

Oterm: Starlette has missing Host header validation that poisons request.url.path, bypassing path-based security

Affects Kludex otermSource GCVE Database

0
Compare
Authoritative record:CVE-2026-48710· Medium 6.5

Exploited in the wild · KEV due 16 Sep 2026 · public detection template (Nuclei) : upgrade to 0.17.2_1 now.

Data as of 1 Nov 2026, 02:07 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
KEV deadline
 US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
Patch
Available – fixed in 0.17.2_1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 26 May 2026

  2. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: evidence found.

    Listed in CISA KEV 99 days after disclosure

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by GitHub, Inc.

    , 4 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 24 minutes after disclosure

  4. , 99 days after disclosure

  5. KEV remediation due

    US federal deadline

    , 113 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

Upgrade Kludex oterm to 0.17.2_1.

Affected software

ProductAffectedFixed in
Homebrewotermpkg:brew/otermOther threatsAffected
  • >=0.13.1 <0.17.2_1
Fixed in
  • 0.17.2_1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

A vulnerability in Starlette versions >=0.13.1 and <0.17.2_1 allows an attacker to send a malformed HTTP Host header that causes the reconstructed request.url.path to differ from the actual requested path. This discrepancy can bypass security checks that rely on request.url.path for path-based authorization. The issue is fixed in version 0.17.2_1. The impact depends on application design, specifically if security decisions are based on request.url.path rather than the canonical ASGI path. Reverse proxies that validate Host headers can mitigate this risk.

References

Community reviews

Loading reviews…