Skip to content
Applications

CVE-2026-71024

8.2
High
EPSS 0.33%Patch availableAug 19, 2026

Unauthenticated HTTP access to Oracle Commerce Guided Search exposes data and can cause partial DoS

common questions

Is CVE-2026-71024 being exploited?

Not confirmed. CVE-2026-71024 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.33% probability of exploitation in the next 30 days.

How severe is CVE-2026-71024?

CVE-2026-71024 is rated High with a CVSS score of 8.2. 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-71024?

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

What does CVE-2026-71024 affect?

CVE-2026-71024 affects Oracle Commerce Guided Search (Forge) 11.4.0, Oracle Commerce Experience Manager 11.4.0, Oracle Commerce 11.4.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-71024?

Apply vendor patch when available; restrict HTTP access, isolate service, and add WAF rules ASAP

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

executive summary
technical analysis
affected
Oracle Commerce Guided Search (Forge) 11.4.0Oracle Commerce Experience Manager 11.4.0Oracle Commerce 11.4.0
impact

Unauthenticated network exploit allows read access to accessible product data (confidentiality high) and can cause partial denial of service.

action required

Immediate action required

affected versions
Oracle Corporation Oracle Commerce Guided Search / Oracle Commerce Experience Manager
  • affected11.4.0

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