Skip to content
Applications

CVE-2026-70715

8.8
High
EPSS 0.35%Patch availableAug 19, 2026

Unauthenticated adjacent-network takeover of Oracle Autonomous Health Framework.

common questions

Is CVE-2026-70715 being exploited?

Not confirmed. CVE-2026-70715 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.35% probability of exploitation in the next 30 days.

How severe is CVE-2026-70715?

CVE-2026-70715 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-70715?

Yes. A fix has been recorded for CVE-2026-70715. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-70715 affect?

CVE-2026-70715 affects Oracle Autonomous Health Framework (Trace File Analyzer), Versions: 26-26.1.0, Version: 26.2.0, Version: 26.3.1, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-70715?

Isolate AHF hosts, restrict access to physical/adjacent network, and apply vendor patch when available.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Oracle Autonomous Health Framework (Trace File Analyzer)Versions: 26-26.1.0Version: 26.2.0Version: 26.3.1Version: 26.5.0Version: 26.5.2
impact

Unauthenticated attacker on same physical/adjacent network segment can fully compromise AHF, enabling complete loss of confidentiality, integrity, and availability.

action required

Immediate action required

affected versions
Oracle Corporation Oracle Autonomous Health Framework
  • affected>= 26 and <= 26.1.0
  • affected26.2.0
  • affected26.3.1
  • affected26.5.0
  • affected26.5.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free