Skip to content
Applications

CVE-2026-60591

9.1
Critical
EPSS 0.42%Patch availableAug 19, 2026

Unauthenticated remote compromise and DoS in Oracle Hospitality Simphony POS.

common questions

Is CVE-2026-60591 being exploited?

Not confirmed. CVE-2026-60591 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.42% probability of exploitation in the next 30 days.

How severe is CVE-2026-60591?

CVE-2026-60591 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-60591?

Yes. A fix has been recorded for CVE-2026-60591. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-60591 affect?

CVE-2026-60591 affects Oracle Hospitality Simphony 19.8-19.8.5, 19.9-19.9.3, 19.10-19.10.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-60591?

Apply vendor patch/mitigations, block/limit HTTP access to POS, isolate affected systems.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Oracle Hospitality Simphony 19.8-19.8.519.9-19.9.319.10-19.10.1
impact

Unauthenticated HTTP attacker can create, delete, or modify POS data and cause repeated crashes (complete DoS).

action required

Patch when possible

affected versions
Oracle Corporation Oracle Hospitality Simphony
  • affected>= 19.8 and <= 19.8.5
  • affected>= 19.9 and <= 19.9.3
  • affected>= 19.10 and <= 19.10.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free