# CVE-2026-91613: Vulnerability in the Oracle Communications Unified Inventory Management product of Oracle Communications (component: Security).


- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-29rp-cv23-c4r7

## What is CVE-2026-91613?

CVE-2026-91613 is a low-severity vulnerability in Oracle Communications Unified Inventory Management, published on 20 Oct 2026. 

### Official description

Vulnerability in the Oracle Communications Unified Inventory Management product of Oracle Communications (component: Security).  Supported versions that are affected are 7.5.0, 7.5.1, 7.6.0, 7.7.0, 7.8.0 and 8.0.1. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Communications Unified Inventory Management executes to compromise Oracle Communications Unified Inventory Management.  Successful attacks of this vulnerability can result in  unauthorized read access to a subset of Oracle Communications Unified Inventory Management accessible data. CVSS 3.1 Base Score 3.3 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N).

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-91613 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91613 is a low-severity vulnerability in Oracle Communications Unified Inventory Management, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-91613 in the wild and no public exploit code.

Affected product: Oracle Communications Unified Inventory Management. 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-91613/ (Markdown: https://insights.sbomify.com/CVE-2026-91613/index.md)
```

## Sources

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

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