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-87369 Overview
CVE-2026-87369 is a denial-of-service vulnerability in the Core component of Oracle Service Bus, part of Oracle Fusion Middleware. An unauthenticated remote attacker can send crafted HTTP requests to cause a hang or repeatable crash, resulting in a complete loss of service availability. The flaw is classified under CWE-400: Uncontrolled Resource Consumption and affects supported versions 12.2.1.4.0 and 14.1.2.0.0. Oracle addressed the issue in the October 2026 Critical Patch Update.
Critical Impact
An unauthenticated attacker with network access over HTTP can trigger a complete denial of service against Oracle Service Bus, disrupting integration and messaging workflows across dependent enterprise applications.
Affected Products
- Oracle Service Bus 12.2.1.4.0
- Oracle Service Bus 14.1.2.0.0
- Oracle Fusion Middleware deployments embedding the above Service Bus versions
Discovery Timeline
- 2026-10-20 - CVE-2026-87369 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-87369
Vulnerability Analysis
Oracle Service Bus is a messaging and service orchestration layer within Oracle Fusion Middleware that mediates between service producers and consumers over HTTP, JMS, and other transports. The vulnerability resides in the Core component and manifests when the service processes attacker-supplied HTTP input. Because exploitation requires no credentials and no user interaction, any system exposing a Service Bus endpoint to a reachable network is at risk.
Successful exploitation causes a hang or a repeatable crash of the Oracle Service Bus process. Downstream services relying on bus-mediated messaging lose connectivity until the process is restarted. In clustered deployments, repeated triggering can propagate the failure across nodes if the same request pattern reaches each instance.
Root Cause
The weakness maps to CWE-400: Uncontrolled Resource Consumption. The Core component fails to constrain resource usage when handling specific HTTP input, allowing a single request flow to exhaust threads, memory, or processing capacity. Oracle has not published low-level technical specifics; refer to the Oracle Critical Patch Update Advisory - October 2026 for authoritative details.
Attack Vector
The attack vector is network-based over HTTP. An unauthenticated attacker sends a crafted request to an exposed Oracle Service Bus endpoint. No privileges or user interaction are required, and the Exploit Prediction Scoring System (EPSS) currently reports a probability of 0.441%. Because many Oracle Service Bus deployments are reachable from internal integration networks or partner connections, lateral exposure increases practical risk even when the service is not internet-facing.
No verified proof-of-concept code is publicly available. The vulnerability is described in prose based on Oracle's advisory; see the Oracle Security Alert - October 2026 for vendor guidance.
Detection Methods for CVE-2026-87369
Indicators of Compromise
- Unexpected hangs, thread pool exhaustion, or JVM crashes in Oracle Service Bus managed servers
- Spikes in HTTP request latency or 5xx responses from Service Bus proxy services
- Repeated identical or malformed HTTP requests to Service Bus endpoints from a single source
- WebLogic server logs showing stuck threads, OutOfMemoryError, or forced restarts of Service Bus containers
Detection Strategies
- Monitor WebLogic and Service Bus logs for stuck-thread warnings and abnormal garbage collection patterns
- Baseline normal HTTP request rates and payload sizes to Service Bus proxies and alert on deviations
- Correlate availability drops with inbound HTTP traffic patterns to identify triggering requests
- Apply web application firewall (WAF) inspection in front of exposed Service Bus endpoints
Monitoring Recommendations
- Enable JMX metrics for thread pool saturation, heap usage, and request queue depth on Service Bus servers
- Forward WebLogic server logs and HTTP access logs to a centralized analytics platform for correlation
- Alert on repeated restarts of Oracle Service Bus managed servers within short time windows
- Track upstream service error rates to detect cascading effects from Service Bus unavailability
How to Mitigate CVE-2026-87369
Immediate Actions Required
- Apply the October 2026 Oracle Critical Patch Update to all affected Oracle Service Bus instances
- Inventory Oracle Fusion Middleware deployments and confirm Service Bus versions 12.2.1.4.0 and 14.1.2.0.0
- Restrict network exposure of Service Bus HTTP endpoints to trusted integration zones
- Validate backup and failover procedures to recover from service hangs during patch rollout
Patch Information
Oracle released a fix as part of the October 2026 Critical Patch Update. Review the patch matrix and apply vendor-supplied updates for Oracle Service Bus 12.2.1.4.0 and 14.1.2.0.0. Full details are published in the Oracle Critical Patch Update Advisory - October 2026.
Workarounds
- Place Service Bus endpoints behind a reverse proxy or WAF with rate limiting and request validation
- Enforce network ACLs restricting inbound HTTP access to known integration clients only
- Configure WebLogic work managers with constrained thread pools and request timeouts to limit resource exhaustion
- Enable health checks and automated restart policies to reduce mean time to recovery during exploitation attempts
# Example: restrict inbound HTTP access to Oracle Service Bus listener
# Replace <TRUSTED_CIDR> and <OSB_PORT> with environment-specific values
iptables -A INPUT -p tcp --dport <OSB_PORT> -s <TRUSTED_CIDR> -j ACCEPT
iptables -A INPUT -p tcp --dport <OSB_PORT> -j DROP
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

