# CVE-2026-101401: Vulnerability in the Siebel Apps - Marketing product of Oracle Siebel CRM (component: Marketing).


- **Severity:** Low 2.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-f8jr-7mrf-w6x2

## What is CVE-2026-101401?

CVE-2026-101401 is a low-severity vulnerability in Oracle Corporation Siebel Apps - Marketing, published on 20 Oct 2026. 

### Official description

Vulnerability in the Siebel Apps - Marketing product of Oracle Siebel CRM (component: Marketing).  Supported versions that are affected are 17.0-26.9. Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where Siebel Apps - Marketing executes to compromise Siebel Apps - Marketing.  Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Siebel Apps - Marketing. CVSS 3.1 Base Score 2.9 (Availability impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L).

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2026-101401 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101401 is a low-severity vulnerability in Oracle Corporation Siebel Apps - Marketing, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-101401 in the wild and no public exploit code.

Affected product: Oracle Corporation Siebel Apps - Marketing. 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-101401/ (Markdown: https://insights.sbomify.com/CVE-2026-101401/index.md)
```

## Sources

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

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