Quick answers
- Is CVE-2026-101763 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-101763 being exploited in the wild.
- How severe is CVE-2026-101763?
- Critical severity, with a CVSS score of 9.8, published 20 October 2026.
- Which products and versions are affected?
- Oracle Communications BRM - Elastic Charging Engine 15.0.0.0.0, 15.0.1.0.0, 15.1.0.0.0, 15.2.0.0.0.
- Is there a fix for CVE-2026-101763?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-101763 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-101763?
- Check whether you run Oracle Communications BRM - Elastic Charging Engine at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An easily exploitable remote code execution vulnerability exists in the cloud-native deployment component of Oracle Communications BRM Elastic Charging Engine, accessible via the RMI (Remote Method Invocation) interface. The vulnerability requires no authentication and can be triggered by a network-based attacker to achieve full system compromise. An unauthenticated fix does not appear to be publicly available for the affected versions.
Affected products
- Oracle Communications BRM Elastic Charging Engine 15.0.0.0.0, 15.0.1.0.0, 15.1.0.0.0, 15.2.0.0.0
Timeline
- 2026-10-20: disclosed