dbcve.org
SplunkApplication

CVE-2016-10126

CRITICAL · 9.8 CVSS v3.0 Published 2017-01-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Splunk Web in Splunk Enterprise 5.0.x before 5.0.17, 6.0.x before 6.0.13, 6.1.x before 6.1.12, 6.2.x before 6.2.12, 6.3.x before 6.3.8, and 6.4.x before 6.4.4 allows remote attackers to conduct HTTP request injection attacks and obtain sensitive REST API authentication-token information via unspecified vectors, aka SPL-128840.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Splunk Web in Splunk Enterprise contains a vulnerability allowing remote attackers to conduct HTTP request injection attacks to obtain sensitive REST API authentication-token information. This enables attackers to steal session tokens and impersonate legitimate users within the Splunk environment.

MitigationUpgrade Splunk Enterprise to version 5.0.17, 6.0.13, 6.1.12, 6.2.12, 6.3.8, or 6.4.4 or later. Restrict network access to Splunk Web interfaces and monitor for unauthorized API access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SplunkApplication
Affected:= 5.0.0= 5.0.1= 5.0.2= 5.0.3= 5.0.4= 5.0.5= 5.0.6= 5.0.7= 5.0.8= 5.0.9= 5.0.10= 5.0.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Splunk Enterprise version
    Run the command: splunk --version or access the Splunk web interface and check About > Version information
    Affected if The version displayed is any of: 5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4, 5.0.5, 5.0.6, 5.0.7, 5.0.8, 5.0.9, 5.0.10, or 5.0.11
  2. Verify Splunk Web interface is enabled
    Check the Splunk configuration file $SPLUNK_HOME/etc/system/default/web.conf for the settings [httpServer] and enableSplunkWeb = 1, or check via Splunk Manager > Server Settings > General Settings
    Affected if Splunk Web is enabled and accessible on port 8000 (default)
  3. Confirm REST API endpoint accessibility
    Attempt to access a REST API endpoint such as https://<splunk_host>:8089/services/server/info or check if port 8089 (Splunk REST API) is listening and exposed
    Affected if The REST API port 8089 is open and reachable from network locations where untrusted users operate

You are affected if you are running Splunk Enterprise versions 5.0.0 through 5.0.11 with Splunk Web enabled and the REST API port accessible to untrusted users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Splunk Enterprise to version 5.0.17, 6.0.13, 6.1.12, 6.2.12, 6.3.8, or 6.4.4 or later. Restrict network access to Splunk Web interfaces and monitor for unauthorized API access.

Recommended fix High confidence

5.0.17

  1. 1. Back up your Splunk configuration and data directory before proceeding with any upgrade
  2. 2. Download Splunk Enterprise version 5.0.17 from the official Splunk website (www.splunk.com)
  3. 3. Stop the Splunk service using: ./splunk stop
  4. 4. Install the upgrade following Splunk's standard upgrade procedure for your operating system
  5. 5. Start the Splunk service using: ./splunk start
  6. 6. Verify the upgrade was successful by checking the Splunk Web interface and confirming the version displays as 5.0.17
  7. 7. Review Splunk release notes for 5.0.17 to ensure all patches are applied and no additional configuration changes are required
Caveat Point release upgrade within 5.0.x branch; review Splunk 5.0.17 release notes for any configuration or feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Splunk Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10126 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-10126 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data