HTTP ServerWeb server / proxy · Oracle

CVE-2026-60438

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-21

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click 4 weeks old

Official description

NVD · unedited

Vulnerability in the Oracle HTTP Server product of Oracle Fusion Middleware (component: mod_ssl). Supported versions that are affected are 12.2.1.4.0 and 14.1.2.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle HTTP Server. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle HTTP Server accessible data as well as unauthorized access to critical data or complete access to all Oracle HTTP Server accessible data. CVSS 3.1 Base Score 9.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).

Technical summary

dbcve analysis · moderate confidence

Critical vulnerability in Oracle HTTP Server's mod_ssl component affecting versions 12.2.1.4.0 and 14.1.2.0.0. The flaw allows unauthenticated remote attackers via HTTP to achieve high confidentiality and integrity impact, potentially creating, modifying, or accessing critical data without authentication.

MitigationApply Oracle Critical Patch Updates for Oracle HTTP Server to address the mod_ssl vulnerability; if patching is immediately unavailable, consider restricting HTTP(s) access to trusted networks only as a temporary measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

HTTP ServerWeb server / proxy

Affected:= 12.2.1.4.0= 14.1.2.0.0

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify Oracle HTTP Server version

Run 'opatch lsinventory' or check the Oracle Inventory at $ORACLE_HOME/oraInventory/ContentsXML/oraclehomeproperties.xml, or use 'ls -la $ORACLE_HOME' to locate version-specific directories

Affected if The installed version is exactly 12.2.1.4.0 or exactly 14.1.2.0.0
Confirm mod_ssl module is loaded

Check the Oracle HTTP Server httpd.conf (typically in $ORACLE_HOME/ohs/modules/ or $ORACLE_HOME/ohs/conf/) for 'LoadModule ssl_module' directive, or run 'httpd -M' if accessible to list loaded modules

Affected if mod_ssl is loaded into the Oracle HTTP Server process
Verify SSL/TLS is actively configured

Examine the SSL configuration file (usually ssl.conf or ssl.conf in $ORACLE_HOME/ohs/conf/ssl.conf) and check if Listen directives with SSL ports (typically 443) are present and enabled in the httpd.conf

Affected if SSL/TLS ports are configured and the server is listening for HTTPS connections
Check SSL/TLS configuration is in use

Review the Oracle HTTP Server virtual host configurations and confirm that SSLEngine is set to 'On' for any active virtual hosts

Affected if SSL virtual hosts are defined and SSLEngine is enabled

You are affected only if your Oracle HTTP Server version is exactly 12.2.1.4.0 or 14.1.2.0.0 AND mod_ssl is loaded AND SSL/TLS is actively configured and accepting connections.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply Oracle Critical Patch Updates for Oracle HTTP Server to address the mod_ssl vulnerability; if patching is immediately unavailable, consider restricting HTTP(s) access to trusted networks only as a temporary measure.

Fix this in HTTP Server Scoped from the published advisory

Consultation8.0 h
Implementation16.0 h
Testing12.0 h
Review / QA8.0 h

44.0 hours of engineering $7,720

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-60438 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-60438 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-60438?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 9.1 Critical

Exploit likelihood EPSS, next 30 days 0.3%

Affects: HTTP Server

Remediation

A high-priority fix

Fix this in HTTP Server 44 hrs · High

Typical engagement from $7,720

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-60438 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References