Quick answers
- Is CVE-2026-46429 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46429 being exploited in the wild.
- How severe is CVE-2026-46429?
- Medium severity, with a CVSS score of 5.5, published 6 November 2026.
- Which products and versions are affected?
- GeoNode <= 5.0.2; geonode (PyPI) <= 5.0.2, ECOSYSTEM:introduced=0,fixed=5.0.3.
- Is there a fix for CVE-2026-46429?
- Yes. geonode (PyPI): upgrade to 5.0.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-46429 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-46429?
- Check whether you run GeoNode or geonode (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
- geonode (PyPI): upgrade to 5.0.3 or later
pip install "geonode>=5.0.3"
Technical details
The upload service validation can be circumvented with specially crafted requests, allowing storage and serving of dangerous file types (CWE-434). The vulnerability requires low privileges and user interaction, is accessible over the network, and affects file integrity and confidentiality. Patch available in version 5.0.3.
Affected products
- GeoNode GeoNode <= 5.0.2
Identifiers
- CVE-2026-46429
- GHSA-fqpv-mq26-pr4j
Timeline
- 2026-11-06: disclosed
- 2026-11-06: advisory