VulnerabilityPublished 20 Jan 2026

CVE-2026-21967: Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Hospitality OPERA 5. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Hospitality OPERA 5 accessible data as well as unauthorized update, insert or delete access to some of Oracle Hospitality OPERA 5 accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Hospitality OPERA 5.

Affects Oracle Hospitality OPERA 5Source CVE Database V5

Not known to be exploited · CVSS 8.6 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Oracle CorporationOracle Hospitality OPERA 5	Affected 5.6.19.23 – 5.6.27.4 4 affected builds	Fixed in–
Mavencom.oracle/Oracle-Hospitality-OPERA-5`pkg:maven/com.oracle/Oracle-Hospitality-OPERA-5`Other threats	Affected 5.6.19.23 – 5.6.27.4 4 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply Oracle's security patches or updates for OPERA 5 as soon as they become available to remediate the vulnerability.
Restrict network access to OPERA 5 HTTP interfaces by implementing strict firewall rules and network segmentation, limiting exposure to trusted internal networks only.
Employ web application firewalls (WAFs) to detect and block suspicious HTTP requests targeting OPERA 5. 4. Monitor network traffic and system logs for unusual access patterns or unauthorized data modifications related to OPERA 5. 5. Conduct regular security assessments and penetration testing focused on OPERA 5 deployments to identify and address potential weaknesses. 6. Implement strong access controls and multi-factor authentication for administrative interfaces to reduce risk from lateral movement post-exploitation. 7. Educate IT and security teams about this vulnerability and ensure incident response plans include scenarios involving OPERA 5 compromise. 8. Consider isolating OPERA 5 systems from the internet and untrusted networks wherever possible to reduce attack surface. 9. Backup critical OPERA 5 data regularly and verify restoration procedures to mitigate impact from potential data tampering or denial of service.

Description

CVE-2026-21967 is a high-severity vulnerability in Oracle Hospitality OPERA 5 affecting versions 5.6.19.23, 5.6.25.17, 5.6.26.10, and 5.

Impact

For European organizations, especially those in the hospitality sector, this vulnerability presents a severe risk. Successful exploitation can lead to unauthorized disclosure of guest and operational data, potentially violating GDPR and other data protection regulations. The ability to modify or delete data could disrupt hotel operations, bookings, billing, and customer service, resulting in financial losses and reputational damage. Partial denial of service could degrade system performance or availability, impacting guest experience and operational continuity. Given the hospitality industry's critical role in Europe's economy and tourism, widespread exploitation could have cascading effects on service providers, partners, and customers. The exposure of sensitive personal data could trigger regulatory fines and legal consequences. Organizations relying on Oracle Hospitality OPERA 5 must consider the risk of targeted attacks by cybercriminals seeking financial gain or espionage, especially in countries with high tourism volumes and international visitors.

References

oracle.com/security-alerts/cpujan2026.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Jan 2026, 20:24 UTC

Technical details

References

Community reviews

Related threats