# CVE-2026-70949: Auth bypass in Siebel CRM Deployment

> A low-privileged attacker can exploit this vulnerability to take over the Siebel CRM Deployment system via network access.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-wjcx-9jg8-xjw3

## What is CVE-2026-70949?

CVE-2026-70949 is a high-severity authentication bypass vulnerability in Oracle Siebel Crm, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the Siebel CRM Deployment product of Oracle Siebel CRM (component: Server Infrastructure).  Supported versions that are affected are 17.0-26.6. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Siebel CRM Deployment.  Successful attacks of this vulnerability can result in takeover of Siebel CRM Deployment. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Siebel Crm.

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

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

## Is CVE-2026-70949 being exploited?

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

## Other vulnerabilities in Oracle Siebel Crm

- [CVE-2026-61317](https://insights.sbomify.com/CVE-2026-61317/): Auth bypass in Siebel CRM Cloud Applications (critical 9.9)
- [CVE-2026-62452](https://insights.sbomify.com/CVE-2026-62452/): Auth bypass in Siebel CRM Cloud Applications (critical 9.9)
- [CVE-2026-62512](https://insights.sbomify.com/CVE-2026-62512/): Auth bypass in Siebel CRM Cloud Applications (critical 9.9)
- [CVE-2026-62588](https://insights.sbomify.com/CVE-2026-62588/): Auth bypass in Siebel CRM Integration (critical 9.9)
- [CVE-2026-60711](https://insights.sbomify.com/CVE-2026-60711/): Auth bypass in Siebel CRM Cloud Applications (critical 9.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-70949 is a high-severity authentication bypass vulnerability in Oracle Siebel Crm, published on 18 Aug 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-70949 in the wild and no public exploit code.

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

## Sources

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

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