Skip to main content
CVE-2025-62727VulnerabilityPublished Updated

Gptme: Starlette vulnerable to O(n^2) DoS via Range header merging in ``starlette.responses.FileResponse``

Affects gptmeSource GCVE Database

0
Compare
Authoritative record:CVE-2025-62727· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 0.29.0_1 soon.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.29.0_1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

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

    No attack traffic recorded by OffSeq Mirage sensors

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

What to do

Upgrade gptme to 0.29.0_1.

Affected software

ProductAffectedFixed in
Homebrewgptmepkg:brew/gptmeOther threatsAffected
  • >=0.28.0 <0.29.0_1
Fixed in
  • 0.29.0_1

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

AI-suggested

A patch is available in Starlette version 0.29.0_1 that addresses this vulnerability. Users should upgrade to this version or later to remediate the issue. No other specific mitigations are indicated by the vendor advisory.

Description

Starlette versions from 0.28.0 up to but not including 0.29.0_1 contain a vulnerability in the FileResponse component where processing of crafted HTTP Range headers leads to quadratic-time complexity. This can be exploited by unauthenticated attackers to cause CPU exhaustion and denial-of-service on endpoints serving files, including StaticFiles and any direct use of FileResponse. The issue arises from inefficient parsing and merging of multiple range requests. A fix is available in version 0.29.0_1.

References

Community reviews

Loading reviews…