Skip to main content

Oracle Communications BRM EUVDEUVD-2026-47302

| CVE-2026-61091 HIGH
Improper Privilege Management (CWE-269)
2026-07-21 secalert_us@oracle.com GHSA-c2q8-xvvx-f29v
7.8
CVSS 3.1 · Vendor: oracle
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain local low-priv logon on BRM host
  2. Delivery
    Target BRM Server component
  3. Exploit
    Exploit local takeover flaw
  4. Execution
    Escalate to full product control
  5. Impact
    Compromise billing/revenue data (C/I/A)

Vulnerability Assessment

Weakness
CWE
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to already hold a valid local logon to the infrastructure where Oracle Communications Billing and Revenue Management executes and to have at least low-level privileges on that host (CVSS PR:L, AV:L). It affects BRM Server in versions 15.0.0.0.0, 15.0.1.0.0, 15.1.0.0.0 and 15.2.0.0.0. The key limiting factor is that the vulnerability is not remotely reachable over the network and is not unauthenticated - the attacker must first obtain a foothold on the billing host; no additional non-default feature toggle or configuration setting is named in the Oracle description, and no user interaction is required (UI:N).

Impact

Signals are moderate and internally consistent: CVSS 3.1 base score is 7.8 (High) driven by full C/I/A impact, but the attack vector is Local (AV:L) and requires existing low privileges (PR:L), which meaningfully narrows the exploitable population to users who already possess a foothold on the BRM host. AC:L and UI:N indicate that once such access exists, exploitation is reliable and requires no victim interaction. There is no EPSS score, no SSVC decision data, no CISA KEV listing, and no POC in the provided data, so there is no evidence of active or automatable exploitation - this reads as a serious-if-you-are-a-target internal escalation issue rather than a mass-exploited internet-facing threat. Note a minor inconsistency in the intelligence: the tags label this 'Information Disclosure', yet the CVSS vector and description assert full integrity and availability impact (takeover); the vector should be treated as authoritative over the tag. Priority is elevated for telecom operators running BRM 15.x because the product handles revenue-critical data, but the Local vector lowers urgency relative to a network-exploitable flaw.

Exploit ScenarioDerived

An insider or an attacker who has already obtained a low-privileged shell on a BRM Server host (for example via a compromised operator or service account) runs a local exploit against the BRM Server component. With no user interaction and low attack complexity, they escalate to full control of the Oracle Communications Billing and Revenue Management instance, allowing them to read, alter or destroy billing and revenue data. No public POC is available in the provided intelligence.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 22, 2026

Local privilege escalation leading to full product takeover affects the BRM Server component of Oracle Communications Billing and Revenue Management versions 15.0.0.0.0, 15.0.1.0.0, 15.1.0.0.0 and 15.2.0.0.0. A low-privileged attacker who already has a logon on the host where BRM executes can leverage this easily-exploitable flaw to fully compromise the product, gaining high impact to confidentiality, integrity and availability. No public exploit identified at time of analysis and it is not listed in CISA KEV, so exploitation is not confirmed in the wild; Oracle addressed it in the July 2026 Critical Patch Update.

RemediationAI

Apply the fixes delivered in the Oracle July 2026 Critical Patch Update - patch available per vendor advisory at https://www.oracle.com/security-alerts/cpujul2026.html; the input does not include a discrete fixed build number, so administrators should follow the CPU matrix for the exact patch corresponding to their installed BRM 15.x release. Because exploitation requires local logon (AV:L, PR:L), the most effective compensating control until patching is to tightly restrict and audit interactive/OS-level access to the BRM Server hosts: limit accounts that can log on to the billing infrastructure, enforce least privilege on BRM service and application accounts, and monitor for anomalous local activity by low-privileged users. These access restrictions have low functional side effects but require operational discipline around account provisioning; they reduce but do not eliminate risk, so patching remains the primary fix.

Affected VersionsENISA

Oracle Communications Billing and Revenue Management 15.1.0.0.0
Oracle Communications Billing and Revenue Management 15.0.1.0.0
Oracle Communications Billing and Revenue Management 15.2.0.0.0
Oracle Communications Billing and Revenue Management 15.0.0.0.0

Affected Packages

euvd oracle_communications_billing_and_revenue_management no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Oracle Communications Billing and Revenue Management (BRM) is an enterprise convergent charging and billing platform used by telecommunications carriers; the affected BRM Server is the core back-end that processes rating, billing and account management logic. The CVSS vector (AV:L) indicates the weakness is reachable only by a principal with local logon to the infrastructure, and the S:U (unchanged scope) with full C/I/A impact implies the flaw allows an authenticated local user to escalate control over the BRM application/service context itself rather than crossing into a separate security authority. No CWE was supplied by Oracle or NVD, so the precise weakness class (e.g., improper access control, insecure file/permission handling, or injection) cannot be stated with certainty; Oracle's advisory-style description characterizes the outcome as complete 'takeover' of the product.

Know when Communications Billing And Revenue Management gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (oracle) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

Requires existing local logon with low privileges on the BRM host (AV:L, PR:L), reliable once present (AC:L, UI:N), yielding full product takeover so C:H/I:H/A:H with unchanged scope.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (oracle).

CVSS VectorVendor: oracle

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Vulnerability in the Oracle Communications Billing and Revenue Management product of Oracle Communications (component: BRM Server). Supported versions that are affected are 15.0.0.0.0, 15.0.1.0.0, 15.1.0.0.0 and 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).

Executive ViewAI

Why It Matters

Oracle Communications Billing and Revenue Management (BRM Server) contains a privilege escalation vulnerability affecting versions 15.0-15.2, enabling any internal user with system access to gain complete control over the billing system, including sensitive revenue and customer data. This requires immediate patching as it exposes critical revenue infrastructure to insider compromise and operational disruption.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 95% exploitable
Prevalence
Low
niche telecom carrier billing platform, industry-specific deployment
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

CVE-2021-45105 MEDIUM
5.9 Dec 18

Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursio

CVE-2020-35728 HIGH
8.1 Dec 27

FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, rela

CVE-2020-25649 HIGH POC
7.5 Dec 03

A flaw was found in FasterXML Jackson Databind, where it did not have entity expansion secured properly. Rated high seve

CVE-2018-7489 CRITICAL
9.8 Feb 26

FasterXML jackson-databind before 2.7.9.3, 2.8.x before 2.8.11.1 and 2.9.x before 2.9.5 allows unauthenticated remote co

CVE-2019-10086 HIGH
7.3 Aug 20

In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for a

CVE-2016-2381 HIGH
7.5 Apr 08

Perl might allow context-dependent attackers to bypass the taint protection mechanism in a child process via duplicate e

CVE-2021-2351 HIGH POC
8.3 Jul 21

Vulnerability in the Advanced Networking Option component of Oracle Database Server. Rated high severity (CVSS 8.3), thi

CVE-2020-36183 HIGH POC
8.1 Jan 07

FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, rela

CVE-2020-8286 HIGH POC
7.5 Dec 14

curl 7.41.0 through 7.73.0 is vulnerable to an improper check for certificate revocation due to insufficient verificatio

CVE-2020-8285 HIGH POC
7.5 Dec 14

curl 7.21.0 to and including 7.73.0 is vulnerable to uncontrolled recursion due to a stack overflow issue in FTP wildcar

CVE-2020-8203 HIGH POC
7.4 Jul 15

Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20. Rated high severity (CVSS 7.4), this vul

CVE-2020-11022 MEDIUM POC
6.9 Apr 29

In jQuery starting with 1.12.0 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy