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 probability: 0.1%, top 95% of all CVEs by exploit prediction. 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(medium)
- 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
- 4%
- KEV
- Not listed
Published
February 27, 2026
Last Modified
June 17, 2026
Advisory Details (1)
Auto-updated Aug 4, 2026IP Ban Bypass via X-Forwarded-For Header Spoofing · Advisory · kovidgoyal/calibre · GitHub
https://github.com/kovidgoyal/calibre/security/advisories/GHSA-vhxc-r7v8-2xrwAffected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| calibre | 5.12.0+dfsg-1, 5.12.0+dfsg-1+deb11u1, 5.12.0+dfsg-1+deb11u2, 5.12.0+dfsg-1+deb11u3, 5.12.0+dfsg-1+deb11u4 | 5.12.0+dfsg-1+deb11u5 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| calibre | 6.13.0+repack-2 ... 6.13.0+repack-2+deb12u5 (6 versions) | 6.13.0+repack-2+deb12u6 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| calibre | 8.5.0+ds-1, 8.5.0+ds-1+deb13u1 | 8.5.0+ds-1+deb13u2 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| calibre | 8.10.0+ds-1 ... 9.3.1+ds+~0.10.5-1 (41 versions) | 9.4.0+ds+~0.10.5-1 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 28× 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-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-18 18:50 UTCOSV refresh
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 22:04 UTCOSV refresh
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
Show 33 moreShow fewer
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 08:49 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 00:45 UTCEG score recompute
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 08:42 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 08:25 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-07 20:26 UTCEG score recompute
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 02:53 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 04:52 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 19:20 UTCEG score recompute
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 14:03 UTCEG score recompute
- 2026-07-27 13:55 UTCOSV refresh
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
See which npm, PyPI, Go, and Maven packages are affected by 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.