On this page (7 sections)
CVE-2026-91561 is a critical vulnerability in the Core component of Oracle Service Bus, part of Oracle Fusion Middleware. According to the NVD record, a low privileged attacker with network access via RMI can compromise the product, and the impact can reach beyond Service Bus itself. The CVSS 3.1 base score is 9.6.
If you run Oracle Service Bus 12.2.1.4.0 or 14.1.2.0.0, especially with RMI ports reachable from networks you do not fully control, this deserves prompt attention. The public record is short, so this article separates what is confirmed from what you will need to verify in Oracle's own advisory.
What happened
The record was published by the National Vulnerability Database on November 17, 2026 and mirrored to the GitHub Advisory Database on November 18, 2026. Both point to Oracle's security alert page as the vendor reference. The GitHub entry is marked unreviewed and lists no package, affected range or patched version, so it cannot be used to automate version matching.
Only one underlying description exists so far. The NVD text and the GitHub advisory repeat the same wording, so they should not be read as two independent confirmations. We found no separate analysis, proof of concept or exploitation report, and this article does not claim any.
Technical details
The description calls the issue easily exploitable. The CVSS vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N. In plain terms:
| Metric | Value | What it means for you |
|---|---|---|
| Attack vector | Network | Reachable remotely, here via RMI |
| Attack complexity | Low | No special conditions needed |
| Privileges required | Low | Needs some valid low-level access, not admin |
| User interaction | None | No one has to click anything |
| Scope | Changed | Other products or components may be affected |
| Confidentiality / Integrity | High / High | Read and modify access to Service Bus data |
| Availability | None | No denial of service impact rated |
The stated impact is unauthorized creation, deletion or modification of critical data, plus unauthorized access to critical data, covering all data Oracle Service Bus can access. The scope change matters because a service bus typically connects to many backend systems, so data reachable through it may extend beyond the product.
No CWE weakness class is assigned in the record, and the sources give no further detail on the root cause. We will not speculate on how the flaw works.
Who is affected
Per the record, the affected supported versions are 12.2.1.4.0 and 14.1.2.0.0 of Oracle Service Bus. Other versions are not mentioned, so check Oracle's advisory for whether older or unsupported releases are covered.
Realistic exposure depends on two things: whether an attacker can reach the RMI listener, and whether they can obtain a low privileged account. Internal-only deployments are less exposed than those reachable from partner networks, VPN pools or the internet, but a low privilege requirement means a compromised internal account or a malicious insider could be enough. Treat flat internal networks with caution.
How to check your exposure
Start with an inventory. Find every Oracle Service Bus instance, record its version, and note which hosts and ports accept RMI connections.
On the Oracle home of each server, OPatch lists installed patches. This read-only command shows what is applied, so you can compare it against the patch list in Oracle's advisory (run it as the Oracle software owner, with ORACLE_HOME set):
$ORACLE_HOME/OPatch/opatch lsinventoryTo see what is listening on a host, this standard Linux command lists TCP listeners and the owning processes. Look for Java processes of your Service Bus or WebLogic servers and note which addresses they bind to:
ss -tlnpThen confirm from the network side, using your firewall rules or a scan from a separate segment, which of those ports are reachable from outside the intended management and application networks.
What to do now
- Open Oracle's security alert page and find the entry for Oracle Service Bus and CVE-2026-91561, including the patch or fixed version.
- Inventory all Oracle Service Bus 12.2.1.4.0 and 14.1.2.0.0 instances, including test and disaster recovery systems.
- Apply the patch Oracle provides, starting with instances reachable from less trusted networks. Test in staging first.
- Until patched, restrict network access to RMI ports with firewall rules or security groups so only required application and admin hosts can connect.
- Review accounts with access to Service Bus, remove unused ones, and rotate credentials for low-privileged and service accounts that are not essential.
- Review logs and Service Bus configuration for unexpected creation, deletion or changes to services, proxies and stored data since your last known good state.
- Record the patch level and date for each instance so you can prove coverage later.
Detection and monitoring
No indicators of compromise have been published in the sources we reviewed, so detection has to rely on behavior. Watch for RMI connections from unexpected source addresses, new or unusual authentication from low-privileged accounts, and changes to Service Bus configuration or message flows outside change windows. Forward server and audit logs to a central system so they survive a compromise of the host.
Because the vulnerability sits in middleware rather than a public website, outside scanning will not see it directly. If the systems behind your Service Bus feed public sites or checkout flows, monitoring those endpoints for unexpected changes is still useful. Webforta Monitor tracks uptime, certificate, DNS and header changes, which can help you notice side effects, but it does not detect or block this specific flaw.
What is still unconfirmed
- The fixed version or patch identifier is not given in the NVD or GitHub text; confirm it in Oracle's advisory.
- No exploitation in the wild is reported in the sources, but absence of reports is not proof of safety. The CVE data we reviewed shows no CISA KEV listing.
- The root cause and any weakness classification (CWE) are not published.
- The GitHub advisory is unreviewed and lists affected and patched versions as unknown.
For general guidance on prioritizing fixes across your systems, see website security for small business, and browse more vulnerability coverage on the Webforta blog.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
