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-91629 Overview
CVE-2026-91629 affects the Oracle Communications Billing and Revenue Management (BRM) product within the Oracle Communications suite. The vulnerability resides in the Platform component and impacts BRM 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 with logon access to the infrastructure running BRM can exploit the flaw to compromise confidentiality. Successful exploitation grants unauthorized access to critical data or complete access to all BRM-accessible data. Oracle addressed the issue in the October 2026 Critical Patch Update.
Critical Impact
Authenticated local attackers can read all data accessible to the Oracle Communications Billing and Revenue Management application, exposing billing records, customer accounts, 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-91629 published to NVD as part of the Oracle October 2026 Critical Patch Update
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-91629
Vulnerability Analysis
The flaw is categorized as an information disclosure vulnerability in the Platform component of Oracle Communications Billing and Revenue Management. Exploitation requires local access to the infrastructure hosting BRM along with a valid low-privileged account. The attack affects only confidentiality; integrity and availability remain intact. Oracle rates the attack complexity as high, meaning the attacker must satisfy specific preconditions on the target system before the exploit succeeds. When those preconditions are met, the attacker can read sensitive BRM data outside the scope of their assigned privileges.
Root Cause
Oracle has not published a technical breakdown of the underlying defect. Based on the advisory metadata, the issue resides in platform-level handling within BRM that fails to enforce proper access boundaries for authenticated low-privileged users. The scope remains unchanged, so the exposure is confined to resources already managed by the vulnerable BRM instance.
Attack Vector
The attack vector is local. An attacker must authenticate to the host where BRM runs and interact with the vulnerable Platform component. There is no network-reachable attack path and no user interaction is required from an administrator or other victim. No public proof-of-concept exploit code has been published, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. The EPSS score is 0.1%, indicating a low near-term likelihood of observed exploitation.
No verified exploitation code is available. Refer to the Oracle Security Advisory - CPU October 2026 for vendor technical details.
Detection Methods for CVE-2026-91629
Indicators of Compromise
- Unexpected local logons to BRM application servers from accounts that rarely access the host interactively.
- BRM Platform component queries or process executions that return large volumes of billing or customer data outside normal job windows.
- Shell history or audit records showing low-privileged users invoking BRM Platform utilities beyond their job function.
Detection Strategies
- Enable OS-level auditing (auditd on Linux or Windows Security event logging) on BRM hosts and alert on access to BRM configuration and data directories by non-administrative accounts.
- Correlate BRM application logs with host authentication events to identify low-privileged accounts invoking Platform operations.
- Baseline normal data-read volumes per BRM user role and alert on statistically significant deviations.
Monitoring Recommendations
- Forward BRM application, database, and host logs to a central SIEM for cross-source correlation.
- Monitor privileged file reads under BRM install paths such as $PIN_HOME and alert on access by unexpected UIDs.
- Track interactive sessions on BRM servers and flag any new local account activity against production BRM nodes.
How to Mitigate CVE-2026-91629
Immediate Actions Required
- Apply the Oracle October 2026 Critical Patch Update to all affected BRM 15.x deployments.
- Inventory every BRM 15.0.0.0.0, 15.0.1.0.0, 15.1.0.0.0, and 15.2.0.0.0 instance to confirm patch coverage.
- Review and reduce the set of local accounts authorized to log on to BRM infrastructure hosts.
Patch Information
Oracle released fixes for CVE-2026-91629 as part of the October 2026 Critical Patch Update. Full details and patch download information are available in the Oracle Security Advisory - CPU October 2026.
Workarounds
- Restrict interactive logon rights on BRM servers to a minimal set of administrators until patches are deployed.
- Enforce host-based access controls and jump-server-only access to BRM infrastructure.
- Rotate credentials for any low-privileged accounts that previously held logon access to BRM hosts.
# Example: list local users with interactive logon rights on a BRM Linux host
getent passwd | awk -F: '$7 !~ /(nologin|false)$/ {print $1, $7}'
# Example: enable auditd rules to monitor reads under the BRM install directory
auditctl -w /opt/portal -p r -k brm_platform_read
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

