Skip to main content
Vulnerability Database/CVE-2026-91628

CVE-2026-91628: Oracle Communications Billing Information Disclosure

CVE-2026-91628 is an information disclosure vulnerability in Oracle Communications Billing and Revenue Management that allows low-privileged attackers to access critical data. This article covers technical details, affected versions, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-91628 Overview

CVE-2026-91628 affects the Oracle Communications Billing and Revenue Management (BRM) product, specifically the BRM Server component. Oracle disclosed the issue in the October 2026 Critical Patch Update. A low-privileged attacker with logon access to the infrastructure running BRM can compromise confidentiality of data processed by the application.

Successful exploitation grants unauthorized read access to critical data, up to and including all data accessible to Oracle Communications Billing and Revenue Management. The flaw does not affect integrity or availability. Supported versions 15.0.0.0.0, 15.0.1.0.0, 15.1.0.0.0, and 15.2.0.0.0 are affected.

Critical Impact

An authenticated local attacker can read all data accessible to Oracle Communications Billing and Revenue Management, exposing billing records, customer identifiers, and revenue data.

Affected Products

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

Discovery Timeline

  • 2026-10-20 - CVE-2026-91628 published to NVD alongside the Oracle Critical Patch Update
  • 2026-10-21 - Last updated in NVD database

Technical Details for CVE-2026-91628

Vulnerability Analysis

The vulnerability resides in the BRM Server component of Oracle Communications Billing and Revenue Management. Oracle's advisory classifies it as easily exploitable by an attacker who already has local logon rights to the host running BRM. The attacker needs only low privileges and no user interaction to trigger the condition.

Exploitation targets confidentiality. Oracle states that successful attacks can result in unauthorized access to critical data or complete access to all data reachable by the BRM application. The scope remains unchanged, meaning the attacker gains access only within the BRM security boundary, but that boundary contains sensitive subscriber, billing, and revenue records.

Because BRM commonly stores telecom billing records, customer PII, and payment-related metadata, information disclosure here carries regulatory and financial consequences for operators relying on Oracle Communications.

Root Cause

Oracle has not published a detailed root-cause analysis in the public advisory. The CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) and the "unauthorized access to critical data" wording indicate an access control or information exposure defect in the BRM Server component that improperly grants a low-privileged local account read access to data it should not see.

Attack Vector

The attack vector is local. The attacker must authenticate to the operating system or application tier that hosts BRM Server with at least low privileges, such as an unprivileged shell account or an application role with minimal entitlements. From that foothold, the attacker interacts with BRM Server interfaces to retrieve data outside their authorization boundary.

The vulnerability cannot be triggered remotely without an authenticated local session. Jump-host misuse, shared operations accounts, and compromised service accounts are the realistic abuse paths.

No public proof-of-concept exploit is listed in the enriched data, and the EPSS score is low. Refer to the Oracle CPU Security Alert October 2026 for Oracle's technical description.

Detection Methods for CVE-2026-91628

Indicators of Compromise

  • Unexpected read activity against BRM database schemas or object storage from accounts that do not normally query billing data.
  • Local logons to BRM Server hosts from accounts outside the standard operations and application administration groups.
  • Spikes in BRM API calls or pin_* utility invocations returning large result sets to non-administrative users.

Detection Strategies

  • Baseline normal BRM Server command execution and alert on deviations by low-privileged OS accounts.
  • Correlate operating system authentication logs with BRM application access logs to identify low-privileged users touching customer data.
  • Enable BRM audit logging for sensitive object reads and forward it to a central analytics platform for anomaly detection.

Monitoring Recommendations

  • Monitor local logon events (Linux auth.log, Windows event IDs 4624/4672) on BRM Server hosts for unexpected interactive sessions.
  • Track outbound data transfers from BRM hosts to catch bulk exfiltration following suspicious reads.
  • Review privileged role assignments in BRM monthly to confirm least-privilege alignment.

How to Mitigate CVE-2026-91628

Immediate Actions Required

  • Apply the October 2026 Oracle Critical Patch Update fixes for 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.
  • Audit all local and application accounts on BRM Server hosts and remove unneeded logon rights.
  • Rotate credentials for shared operations accounts that may have had access to BRM infrastructure.

Patch Information

Oracle addressed CVE-2026-91628 in the October 2026 Critical Patch Update. Administrators should consult the Oracle CPU Security Alert October 2026 for patch identifiers, prerequisites, and installation instructions for each affected BRM version.

Workarounds

  • Restrict interactive logon on BRM Server hosts to a minimal set of named administrators enforced through host hardening and jump-host policies.
  • Enforce segregation of duties so that application-tier service accounts cannot be used for interactive sessions.
  • Place BRM infrastructure in a restricted network segment with enhanced monitoring until patches are deployed.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.