Skip to content
ERP

CVE-2026-61175

9.3
Critical
EPSS 0.44%Patch availableJul 22, 2026

Unauthenticated HTTP flaw in Oracle Product Lifecycle Analytics allows data access and partial DoS.

common questions

Is CVE-2026-61175 being exploited?

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

How severe is CVE-2026-61175?

CVE-2026-61175 is rated Critical with a CVSS score of 9.3. 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-61175?

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

What does CVE-2026-61175 affect?

CVE-2026-61175 affects Oracle Product Lifecycle Analytics 3.6.1, Oracle Supply Chain - Product Lifecycle Analytics component. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-61175?

Isolate instances, block HTTP access, monitor, and apply vendor patch when released.

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

executive summary
technical analysis
affected
Oracle Product Lifecycle Analytics 3.6.1Oracle Supply Chain - Product Lifecycle Analytics component
impact

Unauthenticated network attacker can access all Oracle Product Lifecycle Analytics data (confidentiality high) and cause partial denial of service; potential data exfiltration and service disruption.

action required

Immediate action required

affected versions
Oracle Corporation Oracle Product Lifecycle Analytics
  • affected3.6.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