dbcve.org
Hospitality Opera 5 Property ServicesApplication · Oracle

CVE-2026-34311

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-28
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

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 Hospitality OPERA 5 Property Services product of Oracle Hospitality Applications (component: Opera). Supported versions that are affected are 5.6.19.24, 5.6.22, 5.6.25.19, 5.6.27.6 and 5.6.28. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Hospitality OPERA 5 Property Services. Successful attacks of this vulnerability can result in takeover of Oracle Hospitality OPERA 5 Property Services. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

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 · high confidence

Unauthenticated remote code execution vulnerability in Oracle Hospitality OPERA 5 Property Services allows unauthenticated attackers with network access via HTTP to achieve complete system takeover. The CVSS 9.8 score (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) indicates a straightforward network-based attack requiring no privileges or user interaction, enabling full compromise of confidentiality, integrity, and availability.

MitigationApply Oracle's available security patches for the affected versions (5.6.19.24, 5.6.22, 5.6.25.19, 5.6.27.6, 5.6.28). As an interim control, restrict network access to the OPERA 5 services to trusted networks only, preferably through a firewall or VPN, until the patch can be applied.

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
Hospitality Opera 5 Property ServicesApplication
Affected:= 5.6.19.24= 5.6.22= 5.6.25.19= 5.6.27.6= 5.6.28

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 OPERA 5 Property Services is running
    Check running processes or services for Oracle Hospitality OPERA 5 Property Services. On Windows, use Services console or 'sc query' command. On Linux, check for OPERA-related processes or services.
    Affected if The service is present and running on the system
  2. Determine installed version of OPERA 5
    Locate the OPERA 5 installation directory and check version files, or use Oracle-provided version checking utilities. Common locations include the application's bin or config directories.
    Affected if The installed version matches 5.6.19.24, 5.6.22, 5.6.25.19, 5.6.27.6, or 5.6.28
  3. Verify HTTP service exposure
    Check network configuration to determine if the OPERA 5 HTTP service port (typically 8080 or 443) is listening on external network interfaces. Use 'netstat -an' or 'ss -tlnp' to inspect listening ports and bound addresses.
    Affected if The HTTP service is bound to 0.0.0.0 or an externally accessible IP address
  4. Inspect firewall rules
    Review host-based firewall rules (Windows Firewall or iptables) and network perimeter filters to confirm whether the OPERA 5 HTTP port is permitted for untrusted network sources.
    Affected if Inbound HTTP traffic from untrusted networks is allowed to the OPERA 5 service port

You are affected if Oracle Hospitality OPERA 5 Property Services is running with version 5.6.19.24, 5.6.22, 5.6.25.19, 5.6.27.6, or 5.6.28 and its HTTP interface is network-accessible to untrusted sources.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle's available security patches for the affected versions (5.6.19.24, 5.6.22, 5.6.25.19, 5.6.27.6, 5.6.28). As an interim control, restrict network access to the OPERA 5 services to trusted networks only, preferably through a firewall or VPN, until the patch can be applied.

Recommended fix Moderate confidence

5.6.28 or latest available supported Oracle Hospitality OPERA 5 Property Services release (contact Oracle for current supported version)

  1. Contact Oracle Support to obtain the latest patch for Oracle Hospitality OPERA 5 Property Services
  2. Request the specific Critical Patch Update (CPU) that addresses CVE-2026-34311
  3. Apply the patch following Oracle's standard patch application procedure for OPERA 5 Property Services
  4. Verify the patch was applied successfully by checking the OPERA version and testing critical functionality
  5. After patching, validate that the HTTP-based unauthenticated attack vector is no longer exploitable
Caveat Review Oracle's patch documentation for any specific post-patch configuration requirements; standard OPERA upgrades may require compatibility checks with integrated systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hospitality Opera 5 Property Services Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34311 — 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-34311 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