Skip to main content
VulnerabilityPublished Updated

CVE-2026-70700: Oracle Payables · Improper Access Control

Affects Oracle PayablesSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Oracle CorporationOracle PayablesAffected
  • >=12.2.3 <=12.2.15
Fixed in–

AI-suggested

Oracle has released a fix for this vulnerability as part of the August 2026 Critical Security Patch Update. Users of Oracle Payables versions 12.2.3 through 12.2.15 should apply the relevant patches promptly to remediate this issue. Oracle strongly recommends staying on actively supported versions and applying security patches without delay.

Description

CVE-2026-70700 is a vulnerability in Oracle Payables, part of Oracle E-Business Suite versions 12.2.3 through 12.2.15. It allows an unauthenticated attacker with network access via HTTP to cause a denial of service by hanging or crashing the application. The vulnerability has a CVSS 3.1 base score of 7.5, indicating a high severity impact on availability. Oracle has included this fix in its August 2026 Critical Security Patch Update.

References

Community reviews

Loading reviews…