Skip to main content
VulnerabilityPublished

CVE-2026-46429: GeoNode has Unrestricted File Upload

Affects GeoNodeSource GCVE Database

0
Compare
Authoritative record:CVE-2026-46429· Medium 5.5

Not known to be exploited · CVSS 5.5 Medium : upgrade to 5.0.3 when convenient.

Data as of 6 Nov 2026, 20:33 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.5
Patch
Available – fixed in 5.0.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade GeoNode to 5.0.3.

Affected software

ProductAffectedFixed in
PyPIGeoNodeAffected
  • <5.0.3
Fixed in
  • 5.0.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and should be applied by upgrading GeoNode to version 5.0.3 or later. No additional mitigation steps are indicated by the vendor advisory.

Description

GeoNode versions prior to 5.0.3 contain an unrestricted file upload vulnerability that allows attackers to bypass upload validation using specially crafted requests. This flaw enables the storage and serving of malicious files, potentially leading to limited confidentiality, integrity, and availability impacts. The vulnerability is tracked as CVE-2026-46429 and has a medium severity rating with a CVSS score of 5.5. A fix is available in GeoNode version 5.0.3.

References

Community reviews

Loading reviews…