# CVE-2026-61146: Auth bypass in Oracle Commerce Guided Search / Oracle Commerce Experience Manager

> A low-privileged attacker can bypass authentication to take over Oracle Commerce Guided Search and Experience Manager via HTTP.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** 21 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-v32f-pfmh-2v52

## What is CVE-2026-61146?

CVE-2026-61146 is a critical authentication bypass vulnerability in Oracle Commerce Experience Manager, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the Oracle Commerce Guided Search / Oracle Commerce Experience Manager product of Oracle Commerce (component: Content Acquisition System).   The supported version that is affected is 11.4.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Commerce Guided Search / Oracle Commerce Experience Manager.  While the vulnerability is in Oracle Commerce Guided Search / Oracle Commerce Experience Manager, attacks may significantly impact additional products (scope change).  Successful attacks of this vulnerability can result in takeover of Oracle Commerce Guided Search / Oracle Commerce Experience Manager. CVSS 3.1 Base Score 9.9 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).

Weakness: CWE-284 (Improper Access Control), CWE-306 (Missing Authentication for Critical Functionality), CWE-269 (Improper Privilege Management)

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

It affects 2 products.


Products: Oracle Commerce Experience Manager, Oracle Commerce Guided Search.

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

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

## Is CVE-2026-61146 being exploited?

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

## Other vulnerabilities in Oracle Commerce Experience Manager

- [CVE-2026-70995](https://insights.sbomify.com/CVE-2026-70995/): Auth bypass in Oracle Commerce Guided Search / Oracle Commerce Experience Manager (critical 9.8)
- [CVE-2026-61145](https://insights.sbomify.com/CVE-2026-61145/): Auth bypass in Oracle Commerce Guided Search / Oracle Commerce Experience Manager (critical 9.8)
- [CVE-2026-61161](https://insights.sbomify.com/CVE-2026-61161/): Auth bypass in Oracle Commerce Guided Search / Oracle Commerce Experience Manager (critical 9.8)
- [CVE-2026-70998](https://insights.sbomify.com/CVE-2026-70998/): Missing authorization in Oracle Commerce Guided Search / Oracle Commerce Experience Manager (critical 9.3)
- [CVE-2026-70976](https://insights.sbomify.com/CVE-2026-70976/): Missing authorization in Oracle Commerce Guided Search / Oracle Commerce Experience Manager (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61146 is a critical authentication bypass vulnerability in Oracle Commerce Experience Manager, published on 21 Jul 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-61146 in the wild and no public exploit code.

Affected product: Oracle Commerce Experience Manager. 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-61146/ (Markdown: https://insights.sbomify.com/CVE-2026-61146/index.md)
```

## Sources

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

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