# CVE-2026-131267: Sensitive Information Disclosure through the REST API in Splunk SOAR

> A user with System Settings edit rights can make Splunk SOAR send a stored LDAP bind password to a user-controlled host.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-366c-58g3-877v

## What is CVE-2026-131267?

CVE-2026-131267 is a medium-severity information disclosure vulnerability in Splunk SOAR, published on 19 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings view and edit permissions could test a Lightweight Directory Access Protocol authentication provider and cause Splunk SOAR to send a stored directory service account bind password to a host that the user controls.
The vulnerability is possible because Splunk SOAR reuses a stored directory service provider credential when an authentication test uses a different directory service connection destination.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2026-131267?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-131267?

No fix has been published for CVE-2026-131267 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-131267 being exploited?

There is no known exploitation of CVE-2026-131267 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-131267 and fix it if it is affected.

What it is: CVE-2026-131267 is a medium-severity information disclosure vulnerability in Splunk SOAR, published on 19 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-131267 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Splunk SOAR. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-131267/ (Markdown: https://insights.sbomify.com/CVE-2026-131267/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-131267
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-131267
- OSV: https://osv.dev/vulnerability/CVE-2026-131267

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-131267/
Summaries are generated and may contain mistakes; the official description above is the record.
