# CVE-2026-61126: Privilege escalation in Oracle Communications Billing and Revenue Management

> A low-privileged attacker with local access can escalate privileges to fully compromise the Oracle Communications Billing and Revenue Management system.

- **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
- **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-vr53-qrqq-g8vw

## What is CVE-2026-61126?

CVE-2026-61126 is a high-severity vulnerability in Oracle Communications Billing and Revenue Management, 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 Communications Billing and Revenue Management product of Oracle Communications (component: Platform).  Supported versions that are affected are 15.0.0.0.0-15.0.1.0.0 and  15.1.0.0.0-15.2.0.0.0. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Communications Billing and Revenue Management executes to compromise Oracle Communications Billing and Revenue Management.  Successful attacks of this vulnerability can result in takeover of Oracle Communications Billing and Revenue Management. 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-61126?

It affects 1 product.


Products: Oracle Communications Billing and Revenue Management.

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

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

## Is CVE-2026-61126 being exploited?

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

## Other vulnerabilities in Oracle Communications Billing and Revenue Management

- [CVE-2022-21431](https://insights.sbomify.com/CVE-2022-21431/): Auth bypass in Communications Billing and Revenue Management (critical 10.0)
- [CVE-2022-21275](https://insights.sbomify.com/CVE-2022-21275/): Auth bypass in Communications Billing and Revenue Management (critical 10.0)
- [CVE-2022-21389](https://insights.sbomify.com/CVE-2022-21389/): Auth bypass in Communications Billing and Revenue Management (critical 10.0)
- [CVE-2022-21390](https://insights.sbomify.com/CVE-2022-21390/): Auth bypass in Communications Billing and Revenue Management (critical 10.0)
- [CVE-2022-21276](https://insights.sbomify.com/CVE-2022-21276/): Auth bypass in Communications Billing and Revenue Management (critical 9.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61126 is a high-severity vulnerability in Oracle Communications Billing and Revenue Management, 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-61126 in the wild and no public exploit code.

Affected product: Oracle Communications Billing and Revenue 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-61126/ (Markdown: https://insights.sbomify.com/CVE-2026-61126/index.md)
```

## Sources

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

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