Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-60365 – Unauthenticated Remote Full Data Compromise – Oracle HTTP Server 12.2.1.4.0, 14….

Be the first to know when new zero-days emerge:

Summary

CVE-2026-60365 is a critical, unauthenticated network-exploitable vulnerability affecting Oracle HTTP Server (versions 12.2.1.4.0 and 14.1.2.0.0) and the Oracle WebLogic Server Proxy Plug-in (version 15.1.1.0.0). Described by Oracle as "easily exploitable," it allows a remote, unauthenticated attacker with HTTP network access to achieve complete unauthorized access to all data and unauthorized creation, deletion, or modification of critical data across affected systems. It was disclosed on July 21, 2026, as part of Oracle’s July 2026 Critical Patch Update (CPU), and carries a CVSS v3.1 base score of 10.0 (CRITICAL).

Technical details

  • Root cause: The specific CWE has not been assigned in the NVD record at time of publication; Oracle classifies the vulnerability as "easily exploitable" with no mitigating preconditions.
  • Trigger conditions: An unauthenticated attacker with network access via HTTP can directly trigger the vulnerability — no credentials, no user interaction, and no special configuration are required.
  • Attack vector: Remote, over the network (AV:N), with low attack complexity (AC:L), requiring no privileges (PR:N) and no user interaction (UI:N).
  • Scope change: The vulnerability carries a Changed scope (S:C), meaning successful exploitation can impact resources and components beyond the directly vulnerable Oracle HTTP Server process itself.
  • Impact: High confidentiality impact (C:H) — complete unauthorized read access to all accessible data; High integrity impact (I:H) — unauthorized creation, deletion, and modification of critical data. Availability is not impacted (A:N).

Affected software

  • Oracle HTTP Server 12.2.1.4.0
  • Oracle HTTP Server 14.1.2.0.0
  • Oracle WebLogic Server Proxy Plug-in 15.1.1.0.0

Severity

CVSS v3.1 Base Score: 10.0 (CRITICAL)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate action: Apply Oracle’s July 2026 Critical Patch Update (CPU), which contains the official fix for CVE-2026-60365. Oracle patch availability details for Fusion Middleware (including Oracle HTTP Server) are published in the "Affected Products and Patch Information" table of the official advisory at oracle.com/security-alerts/cpujul2026.html.
  • If patching cannot be applied immediately: Restrict network access to Oracle HTTP Server instances at the perimeter — ensure they are not directly reachable from untrusted networks or the public internet. Apply egress and ingress controls to limit HTTP exposure to authorized source IP ranges only.
  • Prioritize externally exposed instances: Given the zero-authentication requirement and network attack vector, any Oracle HTTP Server instance accessible from the internet should be treated as highest priority for patching.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge