# CVE-2026-91473: Vulnerability in the Oracle HTTP Server product of Oracle Fusion Middleware (component: Web Listener).


- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** GHSA-cmm6-3pcp-j657

## What is CVE-2026-91473?

CVE-2026-91473 is a high-severity vulnerability in Oracle HTTP Server, published on 20 Oct 2026. 

### Official description

Vulnerability in the Oracle HTTP Server product of Oracle Fusion Middleware (component: Web Listener).   The supported version that is affected is 12.2.1.4.0. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle HTTP Server executes to compromise Oracle HTTP Server.  Successful attacks of this vulnerability can result in takeover of Oracle HTTP Server. CVSS 3.1 Base Score 7.8 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-91473 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91473 is a high-severity vulnerability in Oracle HTTP Server, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-91473 in the wild and no public exploit code.

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

## Sources

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

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