GHSA-582q-v28r-7cxr GeoNetwork has ACL bypass on Elasticsearch search when request body omits query field

• Maven org.geonetwork-opensource:geonetwork: >= 4.0.0-alpha.1, <= 4.0.6-0 (no fix yet) • Maven org.geonetwork-opensource:geonetwork: >= 4.2.0, < 4.2.16 → fixed in 4.2.16 • Maven org.geonetwork-opensource:geonetwork: >= 4.4.0, < 4.4.11 → fixed in 4.4.11

Summary GeoNetwork's Elasticsearch-backed search API is responsible for injecting access-control and visibility filters into every request before it reaches the underlying Elasticsearch index. Under certain request conditions, that filtering step does not run, allowing an unauthenticated user to retrieve indexed metadata records that should be restricted, including records limited to specific groups. Details The search proxy layer forwards client-supplied search requests to Elasticsearch after adding GeoNetwork's own access-control and filter clauses. A flaw in how that filter-injection step is triggered means it can be skipped under certain conditions, so the affected request reaches Elasticsearch without the intended access restrictions applied. Impact This is an authorization bypass leading to information disclosure (CWE-862: Missing Authorization). The skipped filter step is responsible for enforcing several layers of access control at once: group-based record visibility, draft record exclusion, record ownership checks, and portal-specific filtering. Any public-facing GeoNetwork 4.x instance (4.0.0-alpha.1 through 4.4.10) is affected. An unauthenticated attacker can retrieve the full contents of metadata records that should not be publicly visible.