How to Fix CVE-2026-7714: Missing Authentication in Calibre-Web-Automated
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-4330: Authorization Bypass Through User-Controlled Key — Authorization Bypass Through User-Controlled Key
- How to Fix CVE-2026-2364: CODESYS Installer TOCTOU Privilege Escalation in CODESYS Installer — CODESYS Installer TOCTOU Privilege Escalation in CODESYS Installer
- How to Fix CVE-2026-5569: Technostrobe HI-LED-WR120-G2 Endpoint access control in HI-LED-WR120-G2 , Technostrobe HI-LED-WR120-G2 Endpoint access control in HI-LED-WR120-G2
- How to Fix CVE-2026-4800: lodash vulnerable to Code Injection via
_.templateimports key names , lodash vulnerable to Code Injection via_.templateimports key names - How to Fix CVE-2026-36767: n/a in n/a , n/a in n/a
*By Sai Kiran Pandrala*
Last verified: 2026-05-25
CVE-2026-7714 is a missing authentication in Calibre-Web-Automated from crocodilestick. Upgrade to the patched build named in the crocodilestick advisory. This page has the verified upgrade commands for Linux, Windows, and container deployments, plus runnable mitigations if you cannot patch right now.
| Severity | CVSS 6.9 - Medium |
|---|---|
| Actively exploited? | Not listed on CISA KEV at time of writing |
| Affected | Calibre-Web-Automated: 4.0.0; Calibre-Web-Automated: 4.0.1; Calibre-Web-Automated: 4.0.2; Calibre-Web-Automated: 4.0.3; Calibre-Web-Automated: 4.0.4; Calibre-Web-Automated: 4.0.5 |
| Fixed in | See vendor advisory for the patched build |
| Type (CWE) | CWE-306: Missing Authentication |
What is CVE-2026-7714?
CVE-2026-7714 is a missing authentication in Calibre-Web-Automated. A flaw has been found in crocodilestick Calibre-Web-Automated up to 4.0.6. Affected by this issue is some unknown functionality of the file cps/cwa_functions.py of the component Admin Endpoint. This manipulation causes missing authentication. It is possible to initiate the attack remotely. The exploit has been published and may be used. Full technical detail is in the vendor advisory and the NVD entry.
Why this CVE matters
The missing authentication class of flaw against Calibre-Web-Automated is the kind of issue attackers chain into broader access once they get a foothold. Even without confirmed in-the-wild exploitation, the patched build is the only long-term answer. Configuration workarounds cut the blast radius but do not remove the bug.
Am I affected?
Run the version check that matches your platform. If the installed build sits inside the affected range from the table above, the fix applies to you.
# Linux package check
dpkg -s calibre-web-automated 2>/dev/null | grep -i version # Debian / Ubuntu
rpm -q calibre-web-automated 2>/dev/null # RHEL / Rocky
How to fix CVE-2026-7714
Apply the patched build the vendor names in the advisory. The commands below are starting points keyed to common platforms; adapt the package name and target version to your environment.
npm / Yarn / pnpm
# Vendor advisory: https://github.com/crocodilestick/Calibre-Web-Automated/pull/1308
# Update to the patched release named in the advisory
npm install calibre-web-automated@latest
# or pin to the exact fixed version from the vendor advisory
npm install calibre-web-automated@<patched-version>
npm ls calibre-web-automated
PyPI (pip / Poetry)
# Vendor advisory: https://github.com/crocodilestick/Calibre-Web-Automated/pull/1308
pip install --upgrade calibre-web-automated
pip show calibre-web-automated | grep -i version
# Poetry:
poetry add calibre-web-automated@^<patched-version>
Docker / container
# Vendor advisory: https://github.com/crocodilestick/Calibre-Web-Automated/pull/1308
docker pull <your-registry>/calibre-web-automated:<patched-tag>
docker stop <app> && docker rm <app>
docker run -d --name <app> <your-registry>/calibre-web-automated:<patched-tag>
PowerShell detect/upgrade/verify/log (Windows)
# CVE-2026-7714 remediation runner. Adapt version checks to your environment.
$log = "C:\Logs\CVE-2026-7714-fix.log"
New-Item -ItemType Directory -Force -Path (Split-Path $log) | Out-Null
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Out-File $log -Append }
try {
Write-Log "Detect: checking installed product"
$installed = Get-CimInstance Win32_Product -ErrorAction SilentlyContinue |
Where-Object { $_.Name -match 'Calibre-Web-Automated' }
if (-not $installed) { Write-Log "Product not installed; nothing to do"; return }
Write-Log "Found version $($installed.Version)"
Write-Log "Backup: copying program files and registry hive"
$stamp = Get-Date -Format yyyyMMdd-HHmm
$backup = "C:\Backup\CVE-2026-7714-$stamp"
New-Item -ItemType Directory -Force -Path $backup | Out-Null
Copy-Item $installed.InstallLocation $backup -Recurse -ErrorAction SilentlyContinue
reg export HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall "$backup\uninstall.reg" /y | Out-Null
Write-Log "Upgrade: install patched build via vendor MSI / Windows Update"
Install-WindowsUpdate -AcceptAll -AutoReboot -ErrorAction SilentlyContinue
Write-Log "Verify: re-reading product version"
$after = Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'Calibre-Web-Automated' }
Write-Log "Post-patch version: $($after.Version)"
if ($after.Version -ne $installed.Version) { Write-Log "SUCCESS: version changed" } else { Write-Log "WARN: version unchanged; check vendor advisory" }
} catch {
Write-Log "ERROR: $_"
throw
}
Bash detect/upgrade/verify/log (Linux)
#!/usr/bin/env bash
# CVE-2026-7714 remediation runner. Re-runnable, exits non-zero on failure.
set -euo pipefail
log() { printf '%s %s\n' "$(date -Is)" "$*" | tee -a /var/log/cve-2026-7714-fix.log; }
log "Detect: current calibre-web-automated version"
if command -v dpkg >/dev/null 2>&1; then
current=$(dpkg-query -W -f='${Version}' calibre-web-automated 2>/dev/null || echo "not-installed")
elif command -v rpm >/dev/null 2>&1; then
current=$(rpm -q --qf '%{VERSION}-%{RELEASE}' calibre-web-automated 2>/dev/null || echo "not-installed")
else
current="unknown"
fi
log "Current: $current"
log "Backup: snapshotting config"
backup="/var/backups/cve-2026-7714-$(date +%Y%m%d-%H%M)"
mkdir -p "$backup"
[ -d /etc/calibre-web-automated ] && cp -a /etc/calibre-web-automated "$backup/" || true
log "Upgrade: applying vendor patch"
if command -v apt-get >/dev/null 2>&1; then
sudo apt-get update -qq
sudo apt-get install -y --only-upgrade calibre-web-automated
elif command -v dnf >/dev/null 2>&1; then
sudo dnf upgrade -y calibre-web-automated
elif command -v yum >/dev/null 2>&1; then
sudo yum update -y calibre-web-automated
fi
log "Verify: re-reading calibre-web-automated version"
if command -v dpkg >/dev/null 2>&1; then
after=$(dpkg-query -W -f='${Version}' calibre-web-automated)
else
after=$(rpm -q --qf '%{VERSION}-%{RELEASE}' calibre-web-automated)
fi
log "After: $after"
if [ "$after" != "$current" ]; then
log "SUCCESS: calibre-web-automated upgraded"
else
log "WARN: version unchanged. Confirm the patched build is in your repository."
exit 1
fi
After the upgrade, restart any service that loads the patched binary so the new code is actually running.
If you can't patch immediately
Patching is the only durable fix. These mitigations cut exposure while the change window is scheduled. They do not remove the vulnerability.
Restrict network exposure (iptables / nftables)
# Replace 10.0.0.0/8 with your management network.
sudo iptables -I INPUT -p tcp --dport 443 -s 10.0.0.0/8 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4
# nftables equivalent
sudo nft add rule inet filter input tcp dport 443 ip saddr != 10.0.0.0/8 drop
How to verify the fix worked
After applying the patched build, confirm the version string matches the fixed release named in the crocodilestick advisory.
dpkg -s calibre-web-automated | grep -i version # Debian / Ubuntu
rpm -q calibre-web-automated # RHEL / Rocky
Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-7714. For internet-facing deployments that were unpatched during the disclosure window, review logs for the affected endpoints over the full exposure period and rotate any credentials the vulnerable process could touch.
Frequently asked questions
Is CVE-2026-7714 being exploited in the wild?
At time of writing, CVE-2026-7714 is not on CISA's KEV list. Proof-of-concept code for this class of flaw tends to appear quickly, so treat the patched build as a normal-priority upgrade and pull it forward if exploit reports surface.
What is the CVSS score for CVE-2026-7714?
The CVSS base score is 6.9 (Medium). Full vector detail is on the NVD entry.
Will a firewall rule or WAF signature fully mitigate CVE-2026-7714?
No. Network-layer filters slow opportunistic scanners and block a subset of payloads, but a focused attacker who knows the bug will work around them. The vendor patch is the only durable fix.
Do I need to assume compromise if the affected service was internet-facing and unpatched?
Not automatically, but log review is cheap insurance. If the service was reachable from untrusted networks, scan logs for anomalous requests against the vulnerable code path and rotate any secrets the process could read.
References
- Official vendor advisory: https://github.com/crocodilestick/Calibre-Web-Automated/pull/1308
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-7714
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://vuldb.com/vuln/360890
- Additional reference: https://vuldb.com/vuln/360890/cti
- Additional reference: https://vuldb.com/submit/806468
- Additional reference: https://github.com/crocodilestick/Calibre-Web-Automated/issues/1304
*Assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*