Quick answers
- Is CVE-2026-61043 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-61043 being exploited in the wild.
- How severe is CVE-2026-61043?
- Medium severity, with a CVSS score of 6.7, 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-61043?
- 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-61043 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-61043?
- 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 classified as a local attack requiring low privileges and human interaction from a victim other than the attacker. The vulnerability involves a scope change (CVSS S:C), meaning an exploit can impact security properties of components outside the immediate Oracle Production Scheduling environment. Attackers can achieve unauthorized creation, deletion, or modification of all accessible data, as well as partial unauthorized read access. The issue was addressed in the Oracle July 2026 Critical Patch Update.
Affected products
- Oracle Production Scheduling 12.2.3-12.2.15
Timeline
- 2026-07-21: advisory: Initial publication by Oracle and NVD