calibre is a cross-platform e-book manager for viewing, converting, editing, and cataloging e-books. Prior to version 9.4.0, the calibre Content Server's brute-force protection mechanism uses a ban key derived from both remote_addr and the X-Forwarded-For header. Since the X-Forwarded-For header is read directly from the HTTP request without any validation or trusted-proxy configuration, an attacker can bypass IP-based bans by simply changing or adding this header, rendering the brute-force protection completely ineffective. This is particularly dangerous for calibre servers exposed to the internet, where brute-force protection is the primary defense against credential stuffing and password guessing attacks. Version 9.4.0 contains a fix for the issue.
CVE-2026-27824
This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(low)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 5%
- KEV
- Not listed
Published
February 27, 2026
Last Modified
June 17, 2026
References (1)
- security-advisories@githubhttps://github.com/kovidgoyal/calibre/security/advisories/GHSA-vhxc-r7v8-2xrw
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 14:03 UTCEG score recompute
- 2026-07-27 13:55 UTCOSV refresh
Related CVEs(same CWE)
Same CWE
10 shownCWE-346 · CWE-307
- CVE-2014-125071NVD 5.5EG 9.8CRITICAL
- CVE-2017-20146EG 9.8CRITICAL
- CVE-2013-10004NVD 6.5EG 9.8CRITICAL
- CVE-2013-4441EG 9.8CRITICAL
- CVE-2018-19879NVD 7.1EG 9.8CRITICAL
- CVE-2018-15723EG 9.8CRITICAL
- CVE-2018-19548EG 9.8CRITICAL
- CVE-2018-15759NVD 9.1EG 9.8CRITICAL
- CVE-2018-11082NVD 6.6EG 9.8CRITICAL
- CVE-2018-12993EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-27824?
When was CVE-2026-27824 disclosed?
Is CVE-2026-27824 actively exploited?
What is the CVSS score of CVE-2026-27824?
How do I remediate CVE-2026-27824?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-27824
Is Your Infrastructure Affected by CVE-2026-27824?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.