CVE-2026-114847 is a critical (CVSS 9.1) flaw in Oracle Autonomous Health Framework versions 26.4 through 26.10. An unauthenticated attacker with network access over HTTP can exploit it to read, create, change or delete critical data.
What Is It
The vulnerability is in the Developer triaging platform component of Oracle Autonomous Health Framework. Oracle describes it as "easily exploitable." An attacker needs no authentication, only network access over HTTP. The weakness is classified as CWE-284 (Improper Access Control).
Oracle rates it CVSS 3.1 base score 9.1 (Critical), with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. That means:
- the attack works over the network
- attack complexity is low
- no privileges or user interaction are needed
- confidentiality and integrity impacts are High
- availability is not affected
Why It Matters
A successful attack can give full access to all data that Oracle Autonomous Health Framework can reach. It can also allow unauthorized creation, deletion or modification of that data.
CISA's SSVC assessment in the NVD record rates the flaw as automatable ("yes") with a "total" technical impact. The same assessment lists exploitation as "none."
The CVE does not currently appear in the CISA Known Exploited Vulnerabilities (KEV) catalog, so KEV does not confirm active exploitation. No KEV remediation deadline or required action applies at this time.
NVD lists the record as "Received," which means NVD has not finished its analysis yet.
What's Vulnerable
- Vendor: Oracle Corporation
- Product: Oracle Autonomous Health Framework
- Component: Developer triaging platform
- Affected versions: 26.4 through 26.10 (supported versions)
The NVD record lists no CPE entries yet.
Patch Status
Oracle published this vulnerability in a security alert, which is linked below. Neither the NVD record nor the CVE.org record names a fixed version.
Administrators running Oracle Autonomous Health Framework 26.4–26.10 should:
- read the Oracle advisory for remediation guidance
- apply the vendor's fix as soon as possible
- limit HTTP network access to affected instances until they are patched, given the critical score and lack of authentication
The CVE is not in the KEV catalog, so there is no CISA-mandated required action or due date.