CVE-2026-76827

What it is

A flaw was found in search-indexer. This vulnerability allows a registered and authenticated managed cluster to tamper with or delete another cluster's indexed search data. This is possible because the delta-sync write paths in search-indexer do not properly restrict UPDATE/DELETE operations to data owned by the calling cluster. An attacker could exploit this by crafting specific user identifiers (UIDs) with a different cluster's prefix.

At a glance

Exploitability

Can be exploited over the network with an admin-level account. High risk of data tampering.

Exploit odds

0.5% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2026-08-19 21:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-26 10:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.5% in the next 30 days (EPSS).
• Severity: 6.8 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2026-08-19 21:17 UTC

Last modified

2026-10-26 10:10 UTC

Exploit probability

0.5% · EPSS, next 30 days

Weakness

CWE-693

Record status

Awaiting Analysis

Attack profile CVSS 3.1 · 6.8

Attack vector

Network

Complexity

Low

Privileges needed

High

User interaction

None

Scope

Changed

Confidentiality

None

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-76827.md and follow it. Check whether this project is affected by CVE-2026-76827. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge