Quick answers
- Is CVE-2026-62518 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62518 being exploited in the wild.
- How severe is CVE-2026-62518?
- High severity, with a CVSS score of 7.6, 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-62518?
- 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-62518 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-62518?
- 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 within the Oracle E-Business Suite, versions 12.2.3 through 12.2.15. It is classified as an easily exploitable flaw that requires low-privileged authentication and is reachable via HTTP over the network. Successful exploitation allows an attacker to gain unauthorized creation, deletion, or modification access to critical application data, as well as limited read access. Additionally, the vulnerability can be used to trigger a partial denial of service (DoS) affecting the availability of the scheduling system. The issue was addressed in the Oracle Critical Patch Update for July 2026.
Affected products
- Oracle Production Scheduling 12.2.3-12.2.15
Timeline
- 2026-07-21: advisory: Oracle published the July 2026 Critical Patch Update containing this fix.
- 2026-07-21: disclosed: CVE record published to the NVD.