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-101575 Overview
CVE-2026-101575 affects the Helidon product of Oracle Fusion Middleware, specifically the Long Running Actions (LRA) component. Supported versions 4.0.0 through 4.5.5 are vulnerable. An unauthenticated attacker with network access over HTTP can compromise Helidon, though exploitation is difficult. The flaw introduces a scope change, meaning attacks originating in Helidon can impact additional products beyond the vulnerable component. Successful exploitation allows unauthorized update, insert, or delete access to a subset of Helidon data, limited read access, and the ability to cause a partial denial of service.
Critical Impact
Unauthenticated network-based attackers can modify data, read limited data, and trigger partial denial of service across Helidon and dependent products through the LRA component.
Affected Products
- Oracle Helidon 4.0.0 through 4.5.5
- Oracle Fusion Middleware deployments using the Helidon LRA (Long Running Actions) component
- Downstream services that integrate with vulnerable Helidon runtimes (scope change)
Discovery Timeline
- 2026-10-20 - CVE CVE-2026-101575 published to NVD
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-101575
Vulnerability Analysis
The vulnerability resides in the LRA (Long Running Actions) component of Oracle Helidon. LRA is a microservice coordination protocol used to manage distributed transactions across loosely coupled services. A flaw in how Helidon processes LRA requests over HTTP allows an unauthenticated remote attacker to alter data state and partially degrade service availability.
The scope change indicates the vulnerable Helidon component can affect resources managed by other components or services. This elevates the practical impact because downstream microservices participating in LRA-coordinated transactions inherit the effect of malicious requests. Oracle rates exploitation difficulty as high, which typically reflects race conditions, specific timing requirements, or constrained preconditions in the request flow.
Root Cause
Oracle has not published a detailed root cause analysis in public references. The advisory indicates the defect lies within Helidon's LRA request handling path, where insufficient validation or authorization allows unauthenticated HTTP clients to influence coordinated transaction state. Review the Oracle Security Alert October 2026 for vendor-provided detail.
Attack Vector
The attack originates over the network via HTTP. No authentication or user interaction is required. The attacker sends crafted requests to Helidon endpoints that process LRA coordination traffic. Successful requests allow partial data modification, limited data disclosure, and partial service disruption in Helidon and participating services.
No public proof-of-concept, exploit code, or verified technical reproduction is available. The vulnerability mechanism is described in prose because no verified exploitation examples exist. Refer to the Oracle Security Alert October 2026 for authoritative guidance.
Detection Methods for CVE-2026-101575
Indicators of Compromise
- Unexpected HTTP requests to Helidon LRA coordinator endpoints (paths containing lra-coordinator or /lra) from untrusted sources.
- Anomalous creation, completion, or cancellation of LRA transactions without matching upstream business activity.
- Partial availability degradation or latency spikes in services participating in LRA-coordinated workflows.
Detection Strategies
- Inspect Helidon access logs for unauthenticated HTTP calls targeting LRA endpoints and correlate with transaction state changes.
- Baseline normal LRA transaction volume per service and alert on deviations that coincide with external HTTP activity.
- Monitor downstream microservices for data writes that lack a corresponding authenticated upstream request.
Monitoring Recommendations
- Enable verbose logging on Helidon LRA components and forward logs to a centralized analytics platform for correlation.
- Deploy a web application firewall or API gateway in front of Helidon services and alert on unauthenticated access to coordination endpoints.
- Track partial service degradation metrics (error rates, timeouts) tied to LRA transaction identifiers.
How to Mitigate CVE-2026-101575
Immediate Actions Required
- Identify all Helidon deployments running versions 4.0.0 through 4.5.5 and inventory services using the LRA component.
- Apply the Oracle Critical Patch Update from the October 2026 cycle as soon as operationally feasible.
- Restrict network exposure of Helidon LRA endpoints to trusted internal networks only, pending patch deployment.
Patch Information
Oracle addressed this vulnerability in the October 2026 Critical Patch Update. Review the Oracle Security Alert October 2026 for patch availability, applicable fixed versions, and installation guidance for affected Helidon releases.
Workarounds
- Place Helidon LRA endpoints behind an authenticated API gateway or reverse proxy that enforces mutual TLS or token-based authentication.
- Apply network segmentation and firewall rules to block external HTTP access to LRA coordinator paths.
- Rate-limit requests to LRA endpoints to reduce the window for timing-dependent exploitation and partial denial of service.
# Configuration example
# Restrict access to Helidon LRA endpoints at the reverse proxy layer
# (nginx example - adapt to your environment)
location /lra-coordinator/ {
allow 10.0.0.0/8;
deny all;
limit_req zone=lra_zone burst=20 nodelay;
proxy_pass http://helidon_backend;
}
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

