Skip to main content

Threats Tagged 'cve-2026-76318'

View all threats tagged with 'cve-2026-76318'. 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: cve-2026-76318

Threats Tagged 'cve-2026-76318'

Click on any threat for detailed analysis and mitigation recommendations

Splunk heeft meerdere kwetsbaarheden verholpen in Splunk Enterprise, specifiek in versies vóór 10.4.2, 10.2.6, 10.0.9 en 9.4.14.

Join the discussion

Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14 contain a vulnerability where a user with the schedule_search capability can store a malicious script in an alert trigger condition field. When another user opens the crafted link, the script executes in their browser and can access all data available to that user. This occurs because Splunk Web does not properly escape special characters in the alert threshold value used in alert trigger condition markup. Exploitation requires user interaction by opening the malicious link.

Join the discussion

CVE-2026-76318 is a cross-site scripting (XSS) vulnerability in Splunk Enterprise versions prior to 10.4.2, 10.2.6, 10.0.9, and 9.4.14. It allows a user with the schedule_search capability to store malicious scripts in alert trigger condition fields. When another user opens a crafted link containing this script, it executes in their browser and can access data available to that user. The issue arises because Splunk Web does not properly escape special characters in alert threshold values used in alert trigger condition markup.

Join the discussion

Showing 1 to 3 of 3 results

Filters:Tag: cve-2026-76318
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses