Quick answers
- Is CVE-2024-41674 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-41674 being exploited in the wild.
- How severe is CVE-2024-41674?
- Low severity, with a CVSS score of 3.1, published 7 July 2026.
- Which products and versions are affected?
- ckan (PyPI) ECOSYSTEM:introduced=2.0.0,fixed=2.10.5.
- Is there a fix for CVE-2024-41674?
- Yes. ckan (PyPI): upgrade to 2.10.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2024-41674 attacked?
- It is attacked over the network.
- Am I affected by CVE-2024-41674?
- Check whether you run ckan (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- ckan (PyPI): upgrade to 2.10.5 or later
pip install "ckan>=2.10.5"
Technical details
The vulnerability is a case of sensitive information disclosure (CWE-209) where error handling in the package_search action fails to sanitize exception messages. When Solr connection failures occur, the raw Solr URL containing embedded credentials is included in the error response without filtering. The attack requires network access to the package_search API endpoint with no authentication required; an attacker can trigger connection errors by calling the API during Solr downtime or network issues. The vulnerability has been patched in CKAN 2.10.5 and 2.11.0.
Affected products
- CKAN Project CKAN 2.0.0 through 2.10.4, excluding 2.10.5 and 2.11.0
Identifiers
- CVE-2024-41674
- GHSA-2rqw-cfhc-35fh
- PYSEC-2026-1248
Timeline
- 2024-08-21: disclosed
- 2024-08-21: patched: Patched in CKAN 2.10.5 and 2.11.0