# CVE-2026-70864: Missing authorization in Oracle Application Testing Suite

> Low-privileged attackers can access critical data and modify some data in Oracle Application Testing Suite via HTTP with user interaction.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-qx42-4v8f-4c89

## What is CVE-2026-70864?

CVE-2026-70864 is a high-severity missing authorization vulnerability in Oracle Application Testing Suite, published on 18 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Vulnerability in Oracle Application Testing Suite.   The supported version that is affected is 13.3.0.1. Easily exploitable vulnerability allows low privileged attacker having Load Testing for Web Apps privilege with network access via HTTP to compromise Oracle Application Testing Suite.  Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Application Testing Suite, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in  unauthorized access to critical data or complete access to all Oracle Application Testing Suite accessible data as well as  unauthorized update, insert or delete access to some of Oracle Application Testing Suite accessible data. CVSS 3.1 Base Score 7.6 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N).

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-70864?

It affects 1 product.


Products: Oracle Application Testing Suite.

## How do I fix CVE-2026-70864?

No fix has been published for CVE-2026-70864 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-70864 being exploited?

There is no known exploitation of CVE-2026-70864 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Application Testing Suite

- [CVE-2026-35290](https://insights.sbomify.com/CVE-2026-35290/): Auth bypass in Oracle Application Testing Suite (critical 9.8)
- [CVE-2026-46876](https://insights.sbomify.com/CVE-2026-46876/): Auth bypass in Oracle Application Testing Suite (critical 9.8)
- [CVE-2026-46924](https://insights.sbomify.com/CVE-2026-46924/): Auth bypass in Oracle Application Testing Suite (critical 9.8)
- [CVE-2019-2904](https://insights.sbomify.com/CVE-2019-2904/): Auth bypass in Enterprise Repository (critical 9.8)
- [CVE-2018-1275](https://insights.sbomify.com/CVE-2018-1275/): Spring Framework has Improperly Implemented Security Check for Standard (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-70864 and fix it if it is affected.

What it is: CVE-2026-70864 is a high-severity missing authorization vulnerability in Oracle Application Testing Suite, published on 18 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-70864 in the wild and no public exploit code.

Affected product: Oracle Application Testing Suite. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-70864/ (Markdown: https://insights.sbomify.com/CVE-2026-70864/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-70864
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-70864
- OSV: https://osv.dev/vulnerability/CVE-2026-70864

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-70864/
Summaries are generated and may contain mistakes; the official description above is the record.