Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-32037: GeoNetwork is a catalog application to manage spatially referenced resources

13
Routine
NONE 0.0REMOTEUPGRADE

CVE-2024-32037 is a none-severity flaw (CVSS 0.0) affecting geonetwork. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

GeoNetwork is a catalog application to manage spatially referenced resources. In versions prior to 4.2.10 and 4.4.5, the search end-point response headers contain information about Elasticsearch software in use. This information is valuable from a security point of view because it allows software used by the server to be easily identified. GeoNetwork 4.4.5 and 4.2.10 fix this issue. No known workarounds are available.

Why this priority

  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score0.0 (None)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.4% (top 68%)
CISA exploited listNo
WeaknessCWE-200
Published2025-02-11
Last modified2026-06-17
Publisher (CNA): GitHub, Inc. · Vendor: osgeo

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

osgeo geonetwork UPGRADE
Affected: < 4.2.10 · >= 4.4.0 and < 4.4.5
Fixed in: 4.2.10, 4.4.5
Safe to downgrade to: a release before 4.4.0
1. Check installed version
apt-cache policy geonetwork || rpm -q geonetwork || geonetwork --version
2. UPGRADE to 4.2.10 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade geonetwork
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade geonetwork
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 4.4.0 (Debian / Ubuntu)
apt-cache madison geonetwork sudo apt install geonetwork=<VERSION_BEFORE_4.4.0> sudo apt-mark hold geonetwork
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list geonetwork sudo dnf downgrade geonetwork-<VERSION_BEFORE_4.4.0> sudo dnf versionlock add geonetwork
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-32037?

geonetwork: upgrade to 4.2.10, 4.4.5. Exact commands for each OS are on this page.

Is CVE-2024-32037 being exploited?

CVE-2024-32037 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-32037 affect?

CVE-2024-32037 affects geonetwork. Severity is none (CVSS 0.0). GeoNetwork is a catalog application to manage spatially referenced resources. In versions prior to 4.2.10 and 4.4.5, the search end-point response headers contain information about Elasticsearch software in use. This information is valuable

How urgent is CVE-2024-32037?

Priority 13/100. Remotely exploitable, no login, no user action

Software pages

Elasticsearch vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.