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-101736 Overview
CVE-2026-101736 is an improper access control vulnerability [CWE-284] in the Core component of Oracle Primavera Unifier, part of Oracle Construction and Engineering. Affected versions range from 21.12.0 through 21.12.17. An unauthenticated remote attacker with network access via HTTP can compromise the application, though exploitation is rated as high complexity. Successful exploitation enables unauthorized creation, modification, or deletion of critical data, and unauthorized read access to all data accessible by Primavera Unifier.
Critical Impact
Unauthenticated network attackers can gain complete read and write access to all Primavera Unifier data, impacting confidentiality and integrity of project, financial, and engineering records.
Affected Products
- Oracle Primavera Unifier 21.12.0 through 21.12.17
- Oracle Construction and Engineering (Core component)
- Deployments exposing Primavera Unifier HTTP interfaces to untrusted networks
Discovery Timeline
- 2026-10-20 - CVE-2026-101736 published to NVD as part of Oracle Critical Patch Update October 2026
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-101736
Vulnerability Analysis
The vulnerability resides in the Core component of Oracle Primavera Unifier, a project lifecycle management platform used across construction, engineering, and capital program delivery. The flaw is classified under [CWE-284] Improper Access Control, meaning the application fails to adequately restrict access to protected resources or functions. An unauthenticated attacker can reach the vulnerable endpoint over HTTP without any user interaction.
Successful exploitation grants read access to all data the Primavera Unifier instance can reach. The same access control weakness allows the attacker to create, modify, or delete critical records. Availability is not directly affected, but data integrity across projects, cost sheets, and workflow records is at risk. Oracle rates the attack complexity as high, indicating that specific conditions outside the attacker's control must align for a successful compromise.
Root Cause
The root cause is improper enforcement of authorization checks within the Core component. According to the Oracle Critical Patch Update advisory, the vulnerable code path does not validate the caller's identity or permissions before processing sensitive requests. This design oversight allows unauthenticated HTTP requests to reach functionality that should require authentication and role-based authorization.
Attack Vector
The attack vector is network-based over HTTP against the Primavera Unifier application tier. No credentials, user interaction, or local access are required. An attacker who can send HTTP requests to an exposed Primavera Unifier instance can attempt exploitation. Instances published to the public internet or reachable from compromised internal segments face the highest risk.
No verified public exploit code is available at the time of writing. See the Oracle Critical Patch Update October 2026 advisory for additional technical context.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-101736
Indicators of Compromise
- Unauthenticated HTTP requests to Primavera Unifier endpoints that return 200 OK responses containing sensitive project or financial data
- Unexpected creation, modification, or deletion events in Unifier audit logs lacking a corresponding authenticated user session
- Anomalous outbound data transfers from the Primavera Unifier application server to untrusted IP addresses
- Access to administrative or API endpoints from source IPs that have not previously authenticated
Detection Strategies
- Review Primavera Unifier application and web server logs for requests to sensitive paths that lack valid session cookies or authentication headers
- Correlate database write events on Unifier tables with authenticated application sessions and flag mismatches
- Deploy web application firewall rules that log and alert on unauthenticated access attempts to Unifier API routes
- Baseline normal request volumes per endpoint and alert on sudden spikes to unauthenticated-reachable paths
Monitoring Recommendations
- Forward Primavera Unifier application, web server, and database audit logs to a centralized SIEM for correlation and retention
- Monitor for configuration changes, user account additions, and permission changes outside approved change windows
- Track HTTP traffic to the Unifier application tier at the network layer to identify scanning or probing behavior
- Alert on access to Primavera Unifier administrative endpoints from source IPs outside approved management ranges
How to Mitigate CVE-2026-101736
Immediate Actions Required
- Apply the Oracle Critical Patch Update October 2026 fixes to all affected Primavera Unifier 21.12.x deployments
- Inventory all Primavera Unifier instances, including non-production and disaster recovery environments, and confirm patch status
- Restrict network access to Primavera Unifier HTTP endpoints to trusted corporate ranges and VPN segments
- Review Unifier audit logs for signs of unauthorized data access or modification since the earliest affected version was deployed
Patch Information
Oracle addressed CVE-2026-101736 in the Oracle Critical Patch Update October 2026. Administrators running Primavera Unifier versions 21.12.0 through 21.12.17 must apply the vendor-supplied patch bundle. Oracle Critical Patch Updates are cumulative, so applying the latest CPU addresses this and other published issues in a single update cycle.
Workarounds
- Place Primavera Unifier behind a reverse proxy or web application firewall that enforces authentication at the network edge
- Remove direct internet exposure of the Unifier application tier where business workflows allow
- Enforce IP allowlisting on the load balancer or firewall for all Unifier HTTP listeners
- Increase audit log retention and review frequency until patching is complete
# Example firewall allowlist for Primavera Unifier HTTP tier
# Replace addresses with your approved management and user ranges
iptables -A INPUT -p tcp --dport 443 -s 10.10.0.0/16 -j ACCEPT
iptables -A INPUT -p tcp --dport 443 -s 192.168.50.0/24 -j ACCEPT
iptables -A INPUT -p tcp --dport 443 -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

