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

New CVE Detected

CVE-2026-60431 – Unauthenticated Information Disclosure via mod_proxy – Oracle HTTP Server 12.2.1…

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

Summary

CVE-2026-60431 is a high-severity information disclosure vulnerability in the mod_proxy component of Oracle HTTP Server, affecting versions 12.2.1.4.0 and 14.1.2.0.0. Published as part of Oracle’s July 21, 2026 Critical Patch Update (CPU), the flaw allows unauthenticated remote attackers to access highly sensitive data across adjacent Oracle Fusion Middleware components, with a CVSS v3.1 base score of 8.6 (HIGH).

Technical details

  • Root cause: The vulnerability resides in Oracle HTTP Server’s mod_proxy component, which inadequately restricts how inbound HTTP requests are forwarded, enabling unauthorized access to resources beyond the server itself.
  • Trigger conditions: No authentication, no user interaction, and no special configuration are required. Attack complexity is rated Low.
  • Attack vector: Remotely exploitable over the network via HTTP. An unauthenticated attacker with network access to the server can trigger the vulnerability directly.
  • Impact: Successful exploitation results in unauthorized read access to critical data. The Scope metric is Changed (S:C), meaning exploitation can affect Oracle Fusion Middleware components beyond the directly targeted Oracle HTTP Server instance. There is no integrity or availability impact.

Affected software

  • Oracle HTTP Server 12.2.1.4.0
  • Oracle HTTP Server 14.1.2.0.0

Severity

  • CVSS v3.1 Base Score: 8.6 (HIGH)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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-60431 for both affected versions (12.2.1.4.0 and 14.1.2.0.0).
  • If patching cannot be applied immediately: Restrict network access to Oracle HTTP Server instances from untrusted or public-facing networks at the perimeter firewall level to reduce exposure until the CPU patch can be deployed.

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