Is CVE-2026-61049 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-61049 being exploited in the wild.

How severe is CVE-2026-61049?

High severity, with a CVSS score of 7.1, 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-61049?

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-61049 attacked?

It is attacked from the adjacent network, in a network appliance.

Am I affected by CVE-2026-61049?

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.

CVE-2026-61049: Oracle Production Scheduling compromise in Internal Operations

CVE-2026-61049 · Severity: high · CVSS 7.1 · Published 2026-07-21

A vulnerability exists in the Internal Operations component of Oracle Production Scheduling, a tool used by manufacturers to optimize supply chain and shop floor operations. An attacker with access to the same local network as the system could potentially take full control of the application. This attack is difficult to perform as it requires a legitimate user to interact with the system during the exploit, but a successful breach could lead to a total loss of data confidentiality and operational integrity.

Technologies: Oracle Production Scheduling. Vendors: Oracle.

Quick answers

Is CVE-2026-61049 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-61049 being exploited in the wild.
How severe is CVE-2026-61049?: High severity, with a CVSS score of 7.1, 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-61049?: 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-61049 attacked?: It is attacked from the adjacent network, in a network appliance.
Am I affected by CVE-2026-61049?: 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 difficult to exploit (AC:H) and requires an unauthenticated attacker to be positioned on the same physical or logical network segment (AV:A) as the target hardware. The exploit also requires human interaction (UI:R) from a legitimate user to succeed. If successful, the attacker can achieve a complete takeover of the Oracle Production Scheduling instance, impacting confidentiality, integrity, and availability. The vulnerability was addressed in the Oracle Critical Patch Update for July 2026.

Affected products

Oracle Production Scheduling (Oracle E-Business Suite) 12.2.3 - 12.2.15

Timeline

2026-07-21: disclosed
2026-07-21: advisory

References

https://www.oracle.com/security-alerts/cpujul2026.html

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.