Quick answers
- Is CVE-2026-62517 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62517 being exploited in the wild.
- How severe is CVE-2026-62517?
- Medium severity, with a CVSS score of 5.3, published 21 July 2026.
- Which products and versions are affected?
- Oracle Production Scheduling 12.2.3-12.2.15.
- Is there a fix for CVE-2026-62517?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-62517 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-62517?
- Check whether you run Oracle Production Scheduling at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability affects the Internal Operations component of Oracle Production Scheduling (versions 12.2.3 through 12.2.15). It is characterized by a high attack complexity, requiring an unauthenticated attacker to have network access via HTTP and necessitating interaction from a legitimate user (UI:R). If successfully exploited, the attacker can achieve unauthorized access to critical data or complete access to all data accessible by the Production Scheduling component. The vulnerability has a CVSS 3.1 base score of 5.3, primarily impacting confidentiality. Users are advised to refer to the Oracle Critical Patch Update for July 2026 for remediation steps.
Affected products
- Oracle Production Scheduling 12.2.3-12.2.15
Timeline
- 2026-07-21: disclosed
- 2026-07-21: advisory