CVE-2026-131225

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.4 from GitHub Security Advisory (severity: MODERATE) published 2026-11-19. A secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-130621 (ENISA EUVD) · GHSA-gfp8-f3jj-5f3g (GitHub Security Advisories)Source: ENISA EUVD

5.4EG
EchelonGraph verdictMonitorNo fix is confirmed yet: check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.4Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (Cisco Systems, Inc.) lists Splunk Enterprise Security versions before 8.7.0 as affected. No release containing a fix is confirmed on record.

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in the Malware data model. Another authenticated user with access to the Malware Search dashboard could later select a table row containing those values. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selected the row. The commands could expose data available to the user who selected the row and add attacker-controlled records to an index. The vulnerability is possible because the Malware Search dashboard does not safely quote row values before adding them to drilldown searches. For more information see Endpoint dashboards (https://help.splunk.com/en/splunk-enterprise-security-8/user-guide/8.4/analytics/endpoint-dashboards) and Users and roles for Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/install/8.7/installation/users-and-roles-for-splunk-enterprise-security) in the Splunk documentation.

CVSS v3
5.4
EG Score
5.4MEDIUMhigh confidence
EG Risk
24
EG Risk 24/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 19, 2026

Last Modified

November 20, 2026

Advisory Details (1)

Auto-updated Nov 20, 2026
No fix on record yet.
Web page

SVD-2026-1106 | Splunk Vulnerability Disclosure

https://advisory.splunk.com/advisories/SVD-2026-1106

Vendor Advisories for CVE-2026-131225(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-11-20 13:28 UTCEchelonGraph re-scored
  4. 2026-11-20 13:28 UTCGHSA enrichmentGHSA-gfp8-f3jj-5f3g · GitHub severity MODERATE · GitHub CVSS 5.4
  5. 2026-11-20 12:59 UTCEchelonGraph re-scored
  6. 2026-11-20 12:58 UTCGHSA enrichmentGHSA-gfp8-f3jj-5f3g · GitHub severity MODERATE · GitHub CVSS 5.4
  7. 2026-11-20 03:14 UTCEchelonGraph re-scored
  8. 2026-11-20 03:14 UTCGHSA enrichmentGHSA-gfp8-f3jj-5f3g · GitHub severity MODERATE · GitHub CVSS 5.4
  9. 2026-11-19 21:03 UTCENISA EUVD ID recordedEUVD-2026-130621 · Source: ENISA EUVD
  10. 2026-11-19 20:29 UTCEchelonGraph re-scored
  11. 2026-11-19 20:03 UTCEchelonGraph re-scoredFirst assessed: 5.4 MEDIUM
  12. 2026-11-19 20:03 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-131225?
CVE-2026-131225 is a medium-severity vulnerability; its CVE record was published on November 19, 2026. In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in the Malware data model. Another authenticated user with access to the Malware Search dashboard could later select a table row containing those…
When was CVE-2026-131225 made public?
CVE-2026-131225 was made public on November 18, 2026: that is the date its CVE record's CNA, Cisco Systems, Inc., gives for when the vulnerability was made public. The CVE record itself was published on November 19, 2026. EchelonGraph's copy of the record carries a last-modified date of November 20, 2026; the record at its source may have been updated since.
Is CVE-2026-131225 actively exploited?
CVE-2026-131225 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-131225?
CVE-2026-131225 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-131225?
No fix for CVE-2026-131225 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (Cisco Systems, Inc.) lists Splunk Enterprise Security versions before 8.7.0 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-131225 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-131225

Explore →

Is Your Infrastructure Affected by CVE-2026-131225?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.