GHSA-2QFR-QMPC-76MM

Vulnerability from github – Published: 2026-11-19 21:31 – Updated: 2026-11-19 21:31
VLAI
Details

In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user could trick an authenticated user into opening a link that the unauthenticated user creates. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the authenticated user. The commands could access data and perform actions available to that user. The vulnerability is possible because the Lookup Editor does not validate lookup identifiers from URL parameters before adding them to searches. The vulnerability requires the attacker to phish the user by tricking them into opening a link that the attacker creates. The unauthenticated user should not be able to exploit the vulnerability at will. For more information see Create and manage lookups in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.0/managing-security-content/create-and-manage-lookups-in-splunk-enterprise-security) in the Splunk documentation.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-131223"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-77"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-11-19T20:17:36Z",
    "severity": "MODERATE"
  },
  "details": "In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user could trick an authenticated user into opening a link that the unauthenticated user creates. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the authenticated user. The commands could access data and perform actions available to that user.\nThe vulnerability is possible because the Lookup Editor does not validate lookup identifiers from URL parameters before adding them to searches.\nThe vulnerability requires the attacker to phish the user by tricking them into opening a link that the attacker creates. The unauthenticated user should not be able to exploit the vulnerability at will.\nFor more information see Create and manage lookups in Splunk Enterprise Security (https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.0/managing-security-content/create-and-manage-lookups-in-splunk-enterprise-security) in the Splunk documentation.",
  "id": "GHSA-2qfr-qmpc-76mm",
  "modified": "2026-11-19T21:31:52Z",
  "published": "2026-11-19T21:31:52Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-131223"
    },
    {
      "type": "WEB",
      "url": "https://advisory.splunk.com/advisories/SVD-2026-1106"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…