Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.

Threats Tagged 'bit-elk-2026-72643'

View all threats tagged with 'bit-elk-2026-72643'. Filter and sort to focus on specific types of threats.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Tag: bit-elk-2026-72643

Threats Tagged 'bit-elk-2026-72643'

Click on any threat for detailed analysis and mitigation recommendations

Elk: Incorrect Authorization in Kibana Agent Builder Leading to Disclosure and Tampering of Private Agents (CVE-2026-72643)CVE-2026-72643
0

CVE-2026-72643 is a high severity vulnerability in Kibana Agent Builder where incorrect authorization logic allows users to access and modify private agents they do not own. The flaw arises because ownership is determined by comparing a stable user identifier or, if absent, the username. Since usernames are not unique across Elasticsearch authentication realms, distinct users with the same username in different realms are treated as the same owner. This leads to unauthorized disclosure and tampering of private agent configurations and instructions.

Join the discussion
CVE-2026-72643: CWE-863 Incorrect Authorization in Elastic KibanaCVE-2026-72643
0

Kibana Agent Builder determines whether a caller owns a private agent by comparing a stable user identifier when one is recorded, and falling back to a comparison of the username when it is not. A username is not unique across Elasticsearch authentication realms, so two distinct principals that share a username in different realms are treated as the same owner. This discloses the configuration and instructions of an agent the caller does not own, and allows that agent to be altered or removed.

Join the discussion

Showing 1 to 2 of 2 results

Filters:Tag: bit-elk-2026-72643
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses