How severe is GHSA-qc4j-v7h6-xr5h?

No CVSS score has been assigned to GHSA-qc4j-v7h6-xr5h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qc4j-v7h6-xr5h?

GHSA-qc4j-v7h6-xr5h affects the following packages: calibreweb (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-qc4j-v7h6-xr5h?

No patched version of calibreweb has shipped for GHSA-qc4j-v7h6-xr5h yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-qc4j-v7h6-xr5h in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for calibreweb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-qc4j-v7h6-xr5h if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-qc4j-v7h6-xr5h?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qc4j-v7h6-xr5h can be triaged on real exposure rather than presence alone.

Is GHSA-qc4j-v7h6-xr5h actively exploited in the wild?

No public exploit code has been indexed for GHSA-qc4j-v7h6-xr5h yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-qc4j-v7h6-xr5h?

GHSA-qc4j-v7h6-xr5h has an EPSS (Exploit Prediction Scoring System) score of 2.8%, placing it in the 86th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-qc4j-v7h6-xr5h?

GHSA-qc4j-v7h6-xr5h is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-qc4j-v7h6-xr5h published, and has it been updated?

GHSA-qc4j-v7h6-xr5h was published on July 24, 2025 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-qc4j-v7h6-xr5h — calibreweb

GHSA-qc4j-v7h6-xr5h is a OS Command Injection vulnerability in calibreweb. No vendor fix is recorded yet; mitigation options are listed below.

Calibre Web and Autocaliweb have OS Command Injection vulnerability

Also known asCVE-2025-7404PYSEC-2026-1235

Published

Jul 24, 2025

Updated

Jul 7, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-qc4j-v7h6-xr5h.

EPSS Exploitation Probability

via FIRST.org ↗

2.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐍calibreweb

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Calibre Web, Autocaliweb allows Blind OS Command Injection. This issue affects Calibre Web: 0.6.24 (Nicolette); Autocaliweb: from 0.7.0 before 0.7.1.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`calibreweb`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for calibreweb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of calibreweb has shipped for GHSA-qc4j-v7h6-xr5h yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-qc4j-v7h6-xr5h can be triaged on real exposure rather than presence alone.

Tailored to GHSA-qc4j-v7h6-xr5h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-qc4j-v7h6-xr5h in your dependencies?

O3 Security finds GHSA-qc4j-v7h6-xr5h across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works