CVE-2026-91624 affects the Product Quality Management component of Oracle Agile Product Lifecycle Management for Process 6.2.4. An unauthenticated attacker with HTTP network access can exploit the vulnerability with low complexity and without user interaction to read, create, delete, or modify critical data or all application-accessible data. The technical root cause and vulnerable function have not been identified. The CVSS v3.1 base score is 9.1, with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in the Product Quality Management component of Oracle Agile Product Lifecycle Management for Process 6.2.4 allows unauthenticated attackers to compromise the application over HTTP without user interaction. Successful exploitation can expose all application-accessible data and permit unauthorized creation, deletion, or modification of critical or all accessible data. The CVSS 3.1 base score is 9.1, with high confidentiality and integrity impacts and no availability impact.
A critical vulnerability affecting the Product Quality Management component of Oracle Agile Product Lifecycle Management for Process 6.2.4. An unauthenticated attacker can exploit it remotely over HTTP without user interaction to read, create, delete, or modify critical data or all data accessible to the application. The reported CVSS v3.1 score is 9.1, with high confidentiality and integrity impacts and no availability impact. The record was received on October 20, 2026; the content does not establish exploit availability, observed exploitation, or patch availability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.