Skip to content
major vulnerability· requires attention

Unauthenticated remote takeover of Oracle Agile PLM 9.3.6 — widely deployed enterprise product; allows full system compromise and likely operational/data impact.

ERP

CVE-2026-71040

9.8
Critical
EPSS 0.47%Patch availableAug 19, 2026

Unauthenticated remote takeover of Oracle Agile PLM 9.3.6 via HTTP

common questions

Is CVE-2026-71040 being exploited?

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

How severe is CVE-2026-71040?

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

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

What does CVE-2026-71040 affect?

CVE-2026-71040 affects Oracle Agile PLM 9.3.6, Oracle Supply Chain / Agile PLM. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-71040?

Isolate Agile PLM from untrusted networks, block HTTP access, apply vendor patch when released, monitor logs

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

executive summary
technical analysis
affected
Oracle Agile PLM 9.3.6Oracle Supply Chain / Agile PLM
impact

Remote unauthenticated full system takeover of Oracle Agile PLM (confidentiality, integrity, availability compromised).

action required

Immediate action required

affected versions
Oracle Corporation Oracle Agile PLM
  • affected9.3.6

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