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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | 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
- 3 Nov 2026, 18:44 UTC Confirmed by the CVE List
- 3 Nov 2026, 19:18 UTC Confirmed by NVD