# GeoNetwork has ACL bypass on Elasticsearch search when request body omits query field

Advisory record · `GHSA-582q-v28r-7cxr`

- **Identifiers:** `GHSA-582q-v28r-7cxr` · `CVE-2026-46487`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 1 Jul 2026
- **Updated:** 1 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 1 Jul 2026, 17:57 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.geonetwork-opensource:geonetwork` (Maven): affected `>=4.0.0-alpha.1, <=4.0.6-0 || >=4.2.0, <4.2.16 || >=4.4.0, <4.4.11`; fixed in `4.2.16`, `4.4.11`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> GeoNetwork versions from 4.0.0-alpha.1 through 4.0.6-0, from 4.2.0 up to but not including 4.2.16, and from 4.4.0 up to but not including 4.4.11 have an access-control bypass in the Elasticsearch-backed search API. When a search request omits the query field, the access-control and visibility filters are not applied, so an unauthenticated user can retrieve metadata records that should be restricted, including group-limited and draft records. Upgrade to GeoNetwork 4.2.16 or 4.4.11, depending on your release line. The source gives few details about the exact request conditions.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0046, the 40th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:20 UTC: First seen by agentprime
- 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-582q-v28r-7cxr)
- 3 Nov 2026, 18:44 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-46487)
- 3 Nov 2026, 19:18 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-46487)

## Sources

- [GitHub Advisory Database: GHSA-582q-v28r-7cxr](https://github.com/advisories/GHSA-582q-v28r-7cxr)
- [OSV: GHSA-582q-v28r-7cxr](https://osv.dev/vulnerability/GHSA-582q-v28r-7cxr)
- <https://github.com/geonetwork/core-geonetwork/security/advisories/GHSA-582q-v28r-7cxr>
- <https://github.com/geonetwork/core-geonetwork>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-582q-v28r-7cxr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-582q-v28r-7cxr/>. Everything for agents: <https://agentprime.io/llms.txt>.