GeoNode is a geospatial content management system, a platform for the management and publication of geospatial data. Prior to 5.1.0, a crafted vector file layer name supplied during upload allows a low-privileged remote user to inject shell syntax and execute arbitrary operating-system commands on the GeoNode server. This issue is fixed in version 5.1.0.
CVE-2026-33050
HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-11-06. A secondary CVSS source baseline 8.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-118477 (ENISA EUVD) · GHSA-9fpx-fr6j-2vh6 (GitHub Security Advisories)Source: ENISA EUVD
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.8Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHhigh confidence
- EG Risk
- 40EG Risk 40/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity88% × 45%Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.7% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.7%
- EPSS %ILE
- 51st
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-08). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 6, 2026
Last Modified
November 9, 2026
Advisory Details (3)
Auto-updated Nov 6, 2026Patch available. Sources: github, github_commit, github_release.
GitHub advisoryMentions a patch (unverified)
OS command injection via uploaded file layer name · Advisory · GeoNode/geonode · GitHub
https://github.com/GeoNode/geonode/security/advisories/GHSA-9fpx-fr6j-2vh6GitHub release Patch Available
5.1.0
Patch available: GeoNode/geonode 5.1.0
https://github.com/GeoNode/geonode/releases/tag/5.1.0GitHub commit Patch Available
commit 1408290c0bb5 (GeoNode/geonode)
Patch available: GeoNode/geonode 5.1.0 (contains commit 1408290c0bb5)
https://github.com/GeoNode/geonode/commit/1408290c0bb54872924a9b334a516db9758a2180Vendor Advisories for CVE-2026-33050(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| pip | GeoNode @ 5.1.0 (fixes < 5.1.0) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| geonode | 2.0 ... 5.0.3.post1 (239 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-11-11 16:39 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-11-10 16:43 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-11-09 13:27 UTCEchelonGraph re-scored
- 2026-11-09 13:27 UTCGHSA enrichmentGHSA-9fpx-fr6j-2vh6 · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-11-09 13:16 UTCEchelonGraph re-scored
- 2026-11-09 13:16 UTCGHSA enrichmentGHSA-9fpx-fr6j-2vh6 · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.7% · 51st percentile
- 2026-11-06 21:47 UTCGHSA enrichmentGHSA-9fpx-fr6j-2vh6 · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-11-06 21:04 UTCENISA EUVD ID recordedEUVD-2026-118477 · Source: ENISA EUVD
- 2026-11-06 20:28 UTCEchelonGraph re-scored
- 2026-11-06 20:28 UTCGHSA enrichmentGHSA-9fpx-fr6j-2vh6 · GitHub severity HIGH · GitHub CVSS 8.8
- 2026-11-06 19:45 UTCEchelonGraph re-scoredFirst assessed: 8.8 HIGH
- 2026-11-06 19:45 UTCGHSA enrichmentGHSA-9fpx-fr6j-2vh6 · GitHub severity HIGH · GitHub CVSS 8.8
Related CVEs(same product + same CWE)
Same product
8 shownPyPI:geonode
Frequently asked(5)
What is CVE-2026-33050?
CVE-2026-33050 is a high-severity vulnerability; its CVE record was published on November 6, 2026. GeoNode is a geospatial content management system, a platform for the management and publication of geospatial data. Prior to 5.1.0, a crafted vector file layer name supplied during upload allows a low-privileged remote user to inject shell syntax and execute arbitrary operating-system commands on…
When was the CVE record for CVE-2026-33050 published?
The CVE record for CVE-2026-33050 was published on November 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 9, 2026; the record at its source may have been updated since.
Is CVE-2026-33050 actively exploited?
CVE-2026-33050 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33050?
CVE-2026-33050 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-33050?
A fix for CVE-2026-33050 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-33050 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33050
Is Your Infrastructure Affected by CVE-2026-33050?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.