Skip to main content
VulnerabilityPublished Updated

CVE-2025-64184: Dosage vulnerable to a Directory Traversal through crafted HTTP responses

Affects dosageSource GCVE Database

0
Compare
Authoritative record:CVE-2025-64184· High 8.8

Not known to be exploited · CVSS 8.8 High : upgrade to 3.2 soon.

Data as of 4 Nov 2026, 18:46 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.8
Patch
Available – fixed in 3.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Nov 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 dosage to 3.2.

Affected software

ProductAffectedFixed in
PyPIdosageAffected
  • <3.2
Fixed in
  • 3.2

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

AI-suggested

Upgrade Dosage to version 3.2 or later where the vulnerability is fixed. There are no known workarounds. Distributors may consider backporting the small, self-contained fix to older versions if upgrading is not immediately feasible.

Description

Dosage versions prior to 3.2 are vulnerable to a directory traversal issue via crafted HTTP responses. The vulnerability arises because Dosage uses the HTTP Content-Type header to determine file extensions when downloading comic images, allowing an attacker to write files outside the intended directory. This flaw is fixed in Dosage 3.2.

References

Community reviews

Loading reviews…