# CVE-2026-101518: Vulnerability in the Oracle Enterprise Manager Base Platform product of Oracle Enterprise Manager (component: Agent Next Gen).


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** 20 Oct 2026
- **Also known as:** GHSA-w3xv-9gx9-v29j

## What is CVE-2026-101518?

CVE-2026-101518 is a high-severity vulnerability in Oracle Enterprise Manager Base Platform, published on 20 Oct 2026. 

### Official description

Vulnerability in the Oracle Enterprise Manager Base Platform product of Oracle Enterprise Manager (component: Agent Next Gen).  Supported versions that are affected are 13.5 and  24.1. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Enterprise Manager Base Platform.  Successful attacks of this vulnerability can result in takeover of Oracle Enterprise Manager Base Platform. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

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


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

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

## Is CVE-2026-101518 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101518 is a high-severity vulnerability in Oracle Enterprise Manager Base Platform, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-101518 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-101518/ (Markdown: https://insights.sbomify.com/CVE-2026-101518/index.md)
```

## Sources

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

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