Is CVE-2026-62447 exploited in the wild?

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

How severe is CVE-2026-62447?

High severity, with a CVSS score of 8.8, published 21 July 2026.

Which products and versions are affected?

Oracle Trade Management 12.2.3-12.2.15.

Is there a fix for CVE-2026-62447?

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

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-62447?

Check whether you run Oracle Trade Management 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-62447: Oracle Trade Management compromise in Claim LOV

CVE-2026-62447 · Severity: high · CVSS 8.8 · Published 2026-07-21

A vulnerability exists in Oracle Trade Management, a component of the Oracle E-Business Suite used by organizations to manage marketing funds and claims. An attacker with basic user access can exploit this flaw to take full control of the Trade Management system. This could lead to the unauthorized access, modification, or deletion of sensitive financial and trade data, potentially disrupting business operations and financial reporting.

Technologies: Oracle Trade Management. Vendors: Oracle.

Quick answers

Is CVE-2026-62447 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-62447 being exploited in the wild.
How severe is CVE-2026-62447?: High severity, with a CVSS score of 8.8, published 21 July 2026.
Which products and versions are affected?: Oracle Trade Management 12.2.3-12.2.15.
Is there a fix for CVE-2026-62447?: 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-62447 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-62447?: Check whether you run Oracle Trade Management 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 Claim LOV (List of Values) component within Oracle Trade Management. It is classified as an easily exploitable flaw that requires only low-privileged authentication and network access via HTTP. While the specific CWE is not detailed in the advisory, the impact is rated for full Confidentiality, Integrity, and Availability loss (takeover). The vulnerability exists in versions 12.2.3 through 12.2.15 of the Oracle E-Business Suite. Organizations are advised to apply the relevant patches from the Oracle Critical Patch Update (CPU) for July 2026.

Affected products

Oracle Trade Management 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.