Skip to main content
VulnerabilityPublished

CVE-2026-46487: core-geonetwork · Missing Authorization

Affects core-geonetworkSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 4.4.11 or 4.2.16 soon.

Data as of 3 Nov 2026, 19:13 UTC

CVSS 3.1 base score
7.5High
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.17.5
Patch
Available – fixed in 4.4.11, 4.2.16
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 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 3 Nov 2026.

What to do

Upgrade core-geonetwork to 4.4.11 or 4.2.16.

Affected software

ProductAffectedFixed in
geonetworkcore-geonetworkAffected
  • >=4.0.0-alpha.1 <=4.0.6-0
  • >=4.2.0 <4.2.16
  • >=4.4.0 <4.4.11
Fixed in
  • 4.4.11
  • 4.2.16

AI-suggested

Upgrade affected GeoNetwork core-geonetwork installations to version 4.2.16 or 4.4.11 or later, where the issue is fixed. No other mitigation or temporary workaround is indicated by the vendor advisory.

Description

CVE-2026-46487 is a missing authorization vulnerability in GeoNetwork core-geonetwork versions from 4.0.0-alpha.1 up to but not including 4.2.16 and 4.4.11. The flaw allows unauthenticated remote attackers to bypass access controls in the Elasticsearch-backed search proxy when a client request omits a query field. This results in unauthorized access to the full indexed metadata records that should be restricted. The issue is fixed in versions 4.2.16 and 4.4.11.

References

Community reviews

Loading reviews…