# CVE-2026-71037: Missing authorization in Oracle Commerce Guided Search / Oracle Commerce Experience Manager > Unauthenticated attackers can modify or read critical data in Oracle Commerce Experience Manager via HTTP, requiring user interaction. - **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 18 Aug 2026 - **Updated:** 19 Aug 2026 - **Also known as:** GHSA-j3cx-rgh2-vxh3 ## What is CVE-2026-71037? CVE-2026-71037 is a critical missing authorization vulnerability in Oracle Commerce Guided Search, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Vulnerability in the Oracle Commerce Guided Search / Oracle Commerce Experience Manager product of Oracle Commerce (component: Experience Manager). The supported version that is affected is 11.4.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Commerce Guided Search / Oracle Commerce Experience Manager. Successful attacks require human interaction from a person other than the attacker and 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 unauthorized creation, deletion or modification access to critical data or all Oracle Commerce Guided Search / Oracle Commerce Experience Manager accessible data as well as unauthorized access to critical data or complete access to all Oracle Commerce Guided Search / Oracle Commerce Experience Manager accessible data. CVSS 3.1 Base Score 9.3 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N). Weakness: CWE-284 (Improper Access Control) ## Which versions are affected by CVE-2026-71037? It affects 1 product. Products: Oracle Commerce Guided Search. ## How do I fix CVE-2026-71037? No fix has been published for CVE-2026-71037 yet. Limit exposure of the affected software until one is available. ## Is CVE-2026-71037 being exploited? There is no known exploitation of CVE-2026-71037 in the wild and no public exploit code. ## Other vulnerabilities in Oracle Commerce Guided Search - [CVE-2022-22947](https://insights.sbomify.com/CVE-2022-22947/): VMware Spring Cloud Gateway Code Injection (critical 10.0, exploited in the wild) - [CVE-2026-71036](https://insights.sbomify.com/CVE-2026-71036/): Privilege escalation in Oracle Commerce Guided Search / Oracle Commerce Experience Manager (critical 9.1) - [CVE-2016-5482](https://insights.sbomify.com/CVE-2016-5482/): Other in n/a (high 8.2) - [CVE-2026-71038](https://insights.sbomify.com/CVE-2026-71038/): Auth bypass in Oracle Commerce Guided Search / Oracle Commerce Experience Manager (high 7.5) - [CVE-2022-21466](https://insights.sbomify.com/CVE-2022-21466/): Information disclosure in Commerce Guided Search / Oracle Commerce Experience Manager (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-71037 and fix it if it is affected. What it is: CVE-2026-71037 is a critical missing authorization vulnerability in Oracle Commerce Guided Search, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-71037 in the wild and no public exploit code. Affected product: Oracle Commerce Guided Search. 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-71037/ (Markdown: https://insights.sbomify.com/CVE-2026-71037/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71037 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71037 - OSV: https://osv.dev/vulnerability/CVE-2026-71037 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-71037/ Summaries are generated and may contain mistakes; the official description above is the record.