Skip to main content
CVE-2025-55165VulnerabilityPublished

CVE-2025-55165: gelbphoenix autocaliweb · Information Exposure

Affects gelbphoenix autocaliwebSource CVE Database V5

0

Not known to be exploited · CVSS 8.3 High : upgrade to 0.8.3 soon.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-25.

What to do

Upgrade gelbphoenix autocaliweb to 0.8.3.

Affected software

ProductAffectedFixed in
gelbphoenix autocaliwebAffected
  • <0.8.3
Fixed in
  • 0.8.3

AI-suggested

1. Immediate upgrade to autocaliweb version 0.8.3 or later, which includes the patch that properly sanitizes debug pack contents. 2. Audit existing debug packs that may have been generated and shared to identify any potential exposure of API keys or other sensitive data. 3. Rotate all API keys and tokens that were included in debug packs generated by vulnerable versions to invalidate potentially compromised credentials. 4. Implement strict access controls and monitoring around the generation and sharing of debug packs to ensure only authorized personnel can create and distribute them. 5. Educate users about the risks of sharing debug packs and establish clear policies for handling diagnostic data containing sensitive information. 6. Consider implementing automated scanning tools to detect sensitive data exposure in debug or log files before they are shared externally. 7. Monitor network and application logs for unusual activity that could indicate misuse of leaked API keys.

Description

Autocaliweb is a web app that offers an interface for browsing, reading, and downloading eBooks using a valid Calibre database. Prior to version 0.8.3, the debug pack generated by Autocaliweb can expose sensitive configuration data, including API keys. This occurs because the to_dict() method, used to serialize configuration for the debug pack, doesn't adequately filter out sensitive fields such as API tokens. Users, unaware of the full contents, might share these debug packs, inadvertently leaking their private API keys. This issue has been patched in version 0.8.3.

References

Community reviews

Loading reviews…