CVE-2026-46429 json
GeoNode: Unrestricted File Upload
published 2026-11-06 2 d ago modified 2026-11-06 2 d ago also GHSA-fqpv-mq26-pr4j , EUVD-2026-118478
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
GeoNode is a geospatial content management system, a platform for the management and publication of geospatial data. Prior to 5.0.3, specially crafted requests can circumvent GeoNode upload service validation, allowing a low-privileged remote user to store and serve malicious files. This issue is fixed in version 5.0.3.
Patch / fix
- pypi geonode 5.0.3
- github.com/GeoNode/geonode@16ec8b3 commit
- github.com/GeoNode/geonode@239a6b4 commit
- github.com/GeoNode/geonode#14223 pull request
- github.com/GeoNode/geonode#14224 pull request
- github.com/GeoNode/geonode/releases/tag/5.0.3 release
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L |
| GitHub | 3.1 | 5.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | geonode | <5.0.3 |
5.0.3 |
Affected products
- GeoNode geonode
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
github.com
/GeoNode/geonode/pull/14223
web
-
github.com
/GeoNode/geonode/pull/14224
web
-
github.com
/GeoNode/geonode/commit/16ec8b3914fe87d0a258c14cf73b0a4295bb072f
web
-
github.com
/GeoNode/geonode/commit/239a6b49c925957197033831df5f20c4c13a14da
web
-
github.com
/GeoNode/geonode/security/advisories/GHSA-fqpv-mq26-pr4j
web
-
github.com
/GeoNode/geonode/releases/tag/5.0.3
web
-
github.com
/GeoNode/geonode
package
Sources
- CVE List CVE-2026-46429
- GitHub Advisory GHSA-fqpv-mq26-pr4j
- NVD CVE-2026-46429
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.