Is CVE-2026-46487 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-46487 being exploited in the wild.

How severe is CVE-2026-46487?

High severity, with a CVSS score of 7.5, published 3 November 2026.

Which products and versions are affected?

org.geonetwork-opensource:geonetwork (Maven) ECOSYSTEM:introduced=4.0.0-alpha.1,last_affected=4.0.6-0.

Is there a fix for CVE-2026-46487?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-46487 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-46487?

Check whether you run org.geonetwork-opensource:geonetwork (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-46487: GeoNetwork ACL bypass in Elasticsearch search API

CVE-2026-46487 · Severity: high · CVSS 7.5 · Published 2026-11-03

GeoNetwork is an open-source catalog application used to manage and publish spatially referenced resources. A security flaw in its search functionality allows unauthorized users to bypass access controls and view private metadata records. This could lead to the exposure of sensitive internal data, draft records, or information restricted to specific organizational groups.

Technologies: org.geonetwork-opensource:geonetwork (Maven). Vendors: Maven.

Quick answers

Is CVE-2026-46487 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-46487 being exploited in the wild.
How severe is CVE-2026-46487?: High severity, with a CVSS score of 7.5, published 3 November 2026.
Which products and versions are affected?: org.geonetwork-opensource:geonetwork (Maven) ECOSYSTEM:introduced=4.0.0-alpha.1,last_affected=4.0.6-0.
Is there a fix for CVE-2026-46487?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-46487 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-46487?: Check whether you run org.geonetwork-opensource:geonetwork (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An authorization bypass (CWE-862) exists in GeoNetwork 4.x's search proxy layer. The application is designed to inject access-control and visibility filters into client-supplied Elasticsearch requests to enforce group-based visibility and ownership checks. However, if a search request body omits the 'query' field, the filter-injection step is skipped, and the request is forwarded to the underlying Elasticsearch index without restrictions. An unauthenticated attacker can exploit this via the network to retrieve the full contents of restricted metadata records. The issue is patched in versions 4.2.16 and 4.4.11.

Affected products

GeoNetwork GeoNetwork >= 4.0.0-alpha.1, <= 4.0.6-0; >= 4.2.0, <= 4.2.15; >= 4.4.0, <= 4.4.10-0

Identifiers

CVE-2026-46487
GHSA-582q-v28r-7cxr

Timeline

2026-07-01: advisory: GitHub Advisory GHSA-582q-v28r-7cxr published
2026-07-01: disclosed: CVE-2026-46487 disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.