BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-76283High confidence

Protection Mechanism Failure in Splunk Enterprise

Splunk · Splunk Enterprise

7.6HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.20% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Splunk Splunk Enterprise and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-94584

No EUVD known-exploited evidence

Protection Mechanism Failure. Splunk addressed multiple internally identified vulnerabilities in Splunk Enterprise versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15. The vulnerabilities are grouped by Common Weakness Enumeration (CWE), with one Common Vulnerabilities and Exposures (CVE) identifier assigned to each group. See Details for more information.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.6 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

Protection Mechanism Failure. Splunk addressed multiple internally identified vulnerabilities in Splunk Enterprise versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15. The vulnerabilities are grouped by Common Weakness Enumeration (CWE), with one Common Vulnerabilities and Exposures (CVE) identifier assigned to each group. See Details for more information.

What

Protection Mechanism Failure. Splunk addressed multiple internally identified vulnerabilities in Splunk Enterprise versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15. The vulnerabilities are grouped by Common Weakness Enumeration (CWE), with one Common Vulnerabilities and Exposures (CVE) identifier assigned to each group. See Details for more information.

Why

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Protection Mechanism Failure. Splunk addressed multiple internally identified vulnerabilities in Splunk Enterprise versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15. The vulnerabilities are grouped by Common Weakness Enumeration (CWE), with one Common Vulnerabilities and Exposures (CVE) identifier assigned to each group. See Details for more information.

Why

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Protection Mechanism Failure → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-693 ↗

CWE-693: Protection Mechanism Failure. The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.ILowIntegrity impact: A successful attack can cause a limited loss.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkCWE-693
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-94584Official EUVD mapping

Protection Mechanism Failure. Splunk addressed multiple internally identified vulnerabilities in Splunk Enterprise versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15. The vulnerabilities are grouped by Common Weakness Enumeration (CWE), with one Common Vulnerabilities and Exposures (CVE) identifier assigned to each group. See Details for more information.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3799Splunk Enterprise: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Splunk Enterprise ausnutzen, um beliebigen Code auszuführen – einschließlich Betriebssystembefehle mit Root-Rechten –, erweiterte Rechte zu erlangen, Sicherheitsmaßnahmen zu umgehen, SQL-Injection durchzuführen sowie Daten zu manipulieren oder offenzulegen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1281Multiples vulnérabilités dans les produits Splunk

d?id=CVE-2026-76274 Référence CVE CVE-2026-76275 https://www.cve.org/CVERecord?id=CVE-2026-76275 Référence CVE CVE-2026-76276 https://www.cve.org/CVERecord?id=CVE-2026-76276 Référence CVE CVE-2026-76277 https://www.cve.org/CVERecord?id=CVE-2026-76277 Référence CVE CVE-2026-76278 https://www.cve.org/CVERecord?id=CVE-2026-76278 Référence CVE CVE-2026-76279 https://www.cve.org/CVERecord?id=CVE-2026-76279 Référence CVE CVE-2026-76280 https://www.cve.org/CVERecord?id=CVE-2026-76280 Référence CVE CVE-2026-76281 https://www.cve.org/CVERecord?id=CVE-2026-76281 Référence CVE CVE-2026-76282 https://www.cve.org/CVERecord?id=CVE-2026-76282 Référence CVE CVE-2026-76283 https://www.cve.org/CVERecord?id=CVE-2026-76283 Référence CVE CVE-2026-76284 https://www.cve.org/CVERecord?id=CVE-2026-76284 Référence CVE CVE-2026-76285 https://www.cve.org/CVERecord?id=CVE-2026-76285 Référence CVE CVE-2026-76286 https://www.cve.org/CVERecord?id=CVE-2026-76286 Référence CVE CVE-2026-8286 https://www.cve.org/CVERecord?id=CVE-2026-8286 Référence CVE CVE-2026-8924 https://www.cve.org/CVERecord?id=CVE-2026-8924 Référence CVE CVE-2026-8926 https://www.cve.org/CVERecord?id=CVE-2026-8926 Référence CVE CVE-2026-8927 https://www.cve.org/CVERecord?id=CVE-2026-8927 Référence CVE CVE-2026-9079 https://www.cve.org/CVERecord?id=CVE-2026-

Official advisory ↗
CSIRT Italia · Italian · rilevate-vulnerabilita-in-prodotti-splunk-5Rilevate vulnerabilità in prodotti Splunk

Rilevate molteplici nuove vulnerabilità in prodotti Splunk, di cui 3 con gravità "critica" e 3 con gravità "alta" in Splunk Enterprise. Tali vulnerabilità, qualora sfruttate, potrebbero consentire ad un utente malintenzionato, in determinate condizioni, di eseguire codice arbitrario, eludere meccanismi di sicurezza ed elevare i propri privilegi sui sistemi interessati.

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0412Kwetsbaarheden verholpen in Splunk Enterprise

Splunk addressed multiple internally discovered vulnerabilities in various versions of Splunk Enterprise, each categorized by CWE and assigned a CVE identifier related to protection mechanism failures.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Splunk Enterprise: 10.2 < 10.2.7, 10.4 < 10.4.3, 10.0 < 10.0.10, 9.4 < 9.4.15
Fixed
Upgrade Splunk Enterprise to versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15, or higher.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 7 Oct 2026 · Last source change 8 Oct 2026, 13:26 UTC · CWE-693 · Protection Mechanism Failure

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-10-08
European sourceENISA EUVD · EUVD-2026-94584
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD awaiting enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    CISA ADP ↗
  2. CVSS scoreCVSS score changed from not recorded to 7.6 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L).
    Before
    not recorded
    After
    7.6 (CVSS 3.1 · CISA ADP · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L)
    CISA ADP ↗
  3. ENISA EUVD mappingEUVD-2026-94584 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-94584"}
    ENISA EUVD ↗
  4. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-94584↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-76283 · cve.blacktree.nl