dbcve.org
HTTP ServerWeb server / proxy · Oracle

CVE-2026-34291

HIGH · 8.7 CVSS v3.1 Published 2026-04-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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.

NVD · unedited
Vulnerability in the Oracle HTTP Server product of Oracle Fusion Middleware (component: Core). Supported versions that are affected are 12.2.1.4.0 and 14.1.2.0.0. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle HTTP Server. While the vulnerability is in Oracle HTTP Server, attacks may significantly impact additional products (scope change). 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 8.7 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N).

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.

dbcve analysis · moderate confidence

Unauthenticated vulnerability in Oracle HTTP Server Core component allows remote attackers via HTTP to create, delete, or modify critical data, plus gain unauthorized read or complete access to all OHS accessible data. The difficult-to-exploit flaw affects versions 12.2.1.4.0 and 14.1.2.0.0 with high confidentiality and integrity impacts and potential scope change to additional products.

MitigationApply Oracle Critical Patch Update for affected versions; until patch availability, restrict network access to OHS endpoints and monitor for unauthorized access attempts.

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

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.

NVD · CPE data
HTTP ServerWeb server / proxy
Affected:= 12.2.1.4.0= 14.1.2.0.0

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.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

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

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.

dbcve checks

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

  1. Identify if Oracle HTTP Server is installed
    Locate OHS processes (such as 'Oracle HTTP Server' or 'mod_weblogic' processes) or check for OHS installation directories typically under $ORACLE_HOME/ohs or C:\Oracle\Middleware\ohs
    Affected if OHS is found running or installed on the system
  2. Determine the installed OHS version
    Check the OHS version file (such as $ORACLE_HOME/ohs/version.txt or Oracle Inventory) or run 'opmnctl status -l' if OPMN is configured, or query the HTTP server headers if accessible
    Affected if The version matches 12.2.1.4.0 or 14.1.2.0.0 exactly
  3. Verify HTTP listeners are accessible
    Check OHS configuration files (httpd.conf, ssl.conf, or ohs.conf) for Listen directives and VirtualHost definitions, and attempt to reach OHS HTTP/HTTPS endpoints from external networks if permitted
    Affected if OHS HTTP ports (default 7777, 8888, or 443/80) are exposed and reachable without proper network segmentation
  4. Inspect OHS configuration for authentication settings
    Review httpd.conf or Oracle HTTP Server's mod_wl_ohs configuration for Require directives and authentication module (mod_auth_basic, OAM, OID) settings
    Affected if Authentication is not enforced or is misconfigured on exposed OHS endpoints

A system is affected if Oracle HTTP Server versions 12.2.1.4.0 or 14.1.2.0.0 are installed and their HTTP listeners are network-accessible without proper authentication controls.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update for affected versions; until patch availability, restrict network access to OHS endpoints and monitor for unauthorized access attempts.

Fix this in HTTP Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34291 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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