# CVE-2026-46991: Missing authorization in Oracle Enterprise Manager Base Platform

> Low-privileged attackers can unauthorizedly read, update, insert, or delete data in Oracle Enterprise Manager Base Platform.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-qf96-48m4-r3c4

## What is CVE-2026-46991?

CVE-2026-46991 is a medium-severity missing authorization vulnerability in Oracle Enterprise Manager Base Platform, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in the Oracle Enterprise Manager Base Platform product of Oracle Enterprise Manager (component: Enterprise Config Management).  Supported versions that are affected are 13.5 and  24.1. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Enterprise Manager Base Platform executes to compromise Oracle Enterprise Manager Base Platform.  Successful attacks of this vulnerability can result in  unauthorized update, insert or delete access to some of Oracle Enterprise Manager Base Platform accessible data as well as  unauthorized read access to a subset of Oracle Enterprise Manager Base Platform accessible data. CVSS 3.1 Base Score 4.4 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N).

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Enterprise Manager Base Platform.

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

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

## Is CVE-2026-46991 being exploited?

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

## Other vulnerabilities in Oracle Enterprise Manager Base Platform

- [CVE-2026-46832](https://insights.sbomify.com/CVE-2026-46832/): Auth bypass in Oracle Enterprise Manager Base Platform (critical 9.9)
- [CVE-2026-46852](https://insights.sbomify.com/CVE-2026-46852/): Privilege escalation in Oracle Enterprise Manager Base Platform (critical 9.9)
- [CVE-2026-46854](https://insights.sbomify.com/CVE-2026-46854/): Auth bypass in Oracle Enterprise Manager Base Platform (critical 9.9)
- [CVE-2026-46855](https://insights.sbomify.com/CVE-2026-46855/): Auth bypass in Oracle Enterprise Manager Base Platform (critical 9.9)
- [CVE-2026-46994](https://insights.sbomify.com/CVE-2026-46994/): Auth bypass in Oracle Enterprise Manager Base Platform (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46991 is a medium-severity missing authorization vulnerability in Oracle Enterprise Manager Base Platform, published on 21 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46991 in the wild and no public exploit code.

Affected product: Oracle Enterprise Manager Base Platform. 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-46991/ (Markdown: https://insights.sbomify.com/CVE-2026-46991/index.md)
```

## Sources

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

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