Quick answers
- Is CVE-2026-33050 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-33050 being exploited in the wild.
- How severe is CVE-2026-33050?
- High severity, with a CVSS score of 8.8, published 6 November 2026.
- Which products and versions are affected?
- GeoNode < 5.1.0; geonode (PyPI) < 5.1.0, ECOSYSTEM:introduced=0,fixed=5.1.0.
- Is there a fix for CVE-2026-33050?
- Yes. geonode (PyPI): upgrade to 5.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-33050 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-33050?
- 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.1.0 or later
pip install "geonode>=5.1.0"
Technical details
The vulnerability is an OS command injection (CWE-78) in GeoNode's file upload handling that fails to sanitize layer names from uploaded vector files before passing them to system commands. An authenticated attacker can upload a specially crafted vector file with shell metacharacters in the layer name to achieve remote code execution. The fix is available in version 5.1.0.
Affected products
- GeoNode GeoNode < 5.1.0
Identifiers
- CVE-2026-33050
- GHSA-9fpx-fr6j-2vh6
Timeline
- 2026-11-05: disclosed
- 2026-11-06: advisory