Introduction
Oracle's November 2026 Critical Security Patch Update fixed an access control flaw in Oracle Autonomous Health Framework (AHF) that lets an unauthenticated attacker with HTTP access read, create, modify, or delete data that AHF can reach. Because AHF ships alongside Oracle Database and Grid Infrastructure, many database teams may be running the affected Developer triaging platform without ever having installed AHF on purpose.
AHF is Oracle's diagnostic and health management framework. It analyzes diagnostic data, monitors systems, detects issues affecting clusters and Oracle RAC databases, notifies administrators, and recommends corrective actions. It bundles tools such as ORAchk, EXAchk, and Trace File Analyzer, and Oracle includes it with Oracle Database and Grid Infrastructure installations and Release Updates. That puts AHF inside the operational tooling of one of the most established enterprise database ecosystems. Oracle reports being named a Leader in Gartner's 2024 Magic Quadrant for Cloud Database Management Systems.
This post summarizes what the public record says about CVE-2026-114847, what Oracle shipped to fix it, and how to confirm the fix is in place.
Technical information
Component and weakness class
Oracle places the vulnerability in the Developer triaging platform component of AHF, reachable over HTTP. The CVE record maps it to CWE 284, Improper Access Control, which MITRE defines as failing to restrict, or incorrectly restricting, access to a resource from an unauthorized actor.
Two caveats apply:
- CWE 284 is a broad Pillar category, and MITRE discourages it for precise mapping. It tells us access restriction is missing or wrong, not which check fails or where.
- AHF is closed source. There is no public commit, diff, or code snippet showing the defect or the change.
The November 2026 advisory contains three AHF fixes. The other two (CVE-2026-19445 and CVE-2026-102274, both in AHFCOMMON) originate in third-party components, Python and PyJWT. CVE-2026-114847 is a flaw in Oracle's own code, in the HTTP-facing Developer triaging platform.
Scoring
Oracle, as the scoring CNA, published this vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N (Base Score 9.1, Critical)
- Attack Vector: Network. The attack path is network based, over HTTP.
- Attack Complexity: Low. Oracle describes it as easily exploitable.
- Privileges Required: None. No account is needed.
- User Interaction: None. No victim action is needed.
- Scope: Unchanged.
- Confidentiality: High and Integrity: High. Serious unauthorized data access and modification are possible.
- Availability: None. This assessment assigns no availability impact. That is a scoring statement, and it does not prove that every operational consequence is impossible.
Attack flow as disclosed
Oracle's description supports the following sequence, and nothing more granular:
- The attacker has network access to the AHF Developer triaging platform over HTTP.
- The attacker sends requests without any credentials and without involving a user.
- Because access to the underlying resource is not correctly restricted, those requests succeed.
- The outcome, per Oracle, can be unauthorized creation, deletion, or modification of critical data or all AHF accessible data, and unauthorized access to critical data or complete access to all AHF accessible data.
The public record does not specify a vulnerable URL, request parameter, HTTP method, payload, exploit code, or indicators of compromise, and it does not establish remote code execution. The impact boundary is Oracle's wording, "AHF accessible data." Given that AHF processes diagnostic data for clusters and RAC databases, that boundary is operationally meaningful, but the record does not claim that connected databases are themselves compromised.
Since no credentials are required, the fix most likely adds authentication or authorization checks in front of the endpoints that read and write AHF data. Oracle has not published root cause details, so treat that as our inference rather than a confirmed description.
Exploitation status
The CISA ADP Vulnrichment SSVC enrichment on the CVE record, timestamped 2026-11-17T23:36:41Z, records:
- Exploitation: none
- Automatable: yes
- Technical Impact: total
These fields answer different questions. "Automatable" describes a technical characteristic, not observed automated attacks. "None" is a dated assessment, not a guarantee. The CVE is absent from the retrieved CISA KEV feed, but that snapshot (catalog version 2026.11.17, released at 17:53 UTC) predates the CVE's publication at 21:31 UTC the same day, so it says nothing either way. The reviewed records identify no threat actor, public exploit, or CVE-specific indicators.
Patch information
Oracle fixed CVE-2026-114847 in the November 2026 Critical Security Patch Update (CSPU), released on 17 November 2026. The AHF risk matrix lists three new security patches, and this CVE is the most severe of them:
- CVE-2026-114847: Developer triaging platform, affected 26.4 through 26.10, CVSS 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N)
- CVE-2026-19445: AHFCOMMON (Python), affected 26.4 through 26.9, CVSS 8.1
- CVE-2026-102274: AHFCOMMON (PyJWT), affected 26.8 through 26.9, CVSS 7.5
What Oracle's CSAF advisory adds
Oracle's machine-readable CSAF file for this update has the most precise remediation data:
- Oracle Bug ID:
40185103, the internal tracking number for the fix. You need it to confirm the fix is installed. - Remediation category:
vendor_fix, offered to "Oracle customers with valid support contracts". - Patch Availability Document:
CPU431on My Oracle Support. The main advisory lists this as the Database family document with patch availability and installation instructions. - Affected product: every AHF release from 26.4 through 26.10.
What is not public
Neither the main advisory nor the CSAF file names a fixed AHF version. Patch files and exact build numbers sit behind My Oracle Support (CPU431). Do not assume a particular later build, such as 26.11, contains the fix until CPU431 confirms it.
Delivering and verifying the fix
The AHF user guide describes two delivery mechanisms, and CPU431 states which one applies to this fix:
- Full upgrade to a newer AHF release with the
ahf_setupinstaller. - Framework update, a ZIP file applied with
ahfctl applyupdate. In a cluster, it must be applied on every node.
The relevant commands from Oracle's documentation:
# Framework update: apply on every node in the cluster ahfctl applyupdate -updatefile <zip> # Show applied framework updates, their status, and the Fixes: field (bug IDs) ahfctl queryupdate -all # Show one update, including the framework files it replaced ahfctl queryupdate -updateid <id> # Revert an update (for this fix, this makes the node vulnerable again) ahfctl rollbackupdate
A patched node should show bug 40185103 in the Fixes: field, or run a release that CPU431 lists as fixed. Querying a specific update ID also lists the framework files it replaced, which is the closest available view of what changed.
Two operational notes:
ahfctl updatewith auto update is documented mainly for metadata (compliance checks and SRDC data collections). Do not assume enabling auto update will install this security fix. Check for bug 40185103 explicitly. Oracle's AHFCTL upgrade procedure also requires root access.- AHF is bundled with Oracle Database and Grid Infrastructure installations and Release Updates, so inventory should include hosts where AHF was never installed separately. Oracle's AHF FAQ points to My Oracle Support document 2550798.1 for obtaining the latest AHF version.
Interim exposure reduction
Oracle's general guidance says blocking the protocol required by an attack may reduce risk until patches are applied. For this CVE, that protocol is HTTP. Oracle also states that such restrictions must be tested on nonproduction systems, may break application functionality, and are not long-term solutions. Oracle's other generic suggestion, removing unnecessary privileges, does not help here because the attack requires no privileges.
Affected systems and versions
- Product: Oracle Autonomous Health Framework (AHF)
- Component: Developer triaging platform
- Affected supported versions: 26.4 through 26.10, inclusive
- Exposure condition: network reachability of the component over HTTP; no authentication or user interaction required
- Deployment note: AHF, including ORAchk, EXAchk, and Trace File Analyzer, is included with Oracle Database and Grid Infrastructure installations and Release Updates, so it may be present on database and cluster hosts without a standalone install
- Fixed version: not publicly named; consult CPU431 and verify bug 40185103 per node
Oracle provides security patches only for product versions under Premier Support or Extended Support, so the supported affected range above is what Oracle has assessed.
Vendor security history
The most relevant recent precedent is in a different Oracle product, Oracle E-Business Suite. Google Threat Intelligence Group and Mandiant reported an extortion campaign by an actor claiming CL0P affiliation. They described exploitation of what may have been CVE-2025-61882 before a patch was available, and successful exfiltration of a significant amount of data in some cases. GTIG did not formally attribute the activity to a tracked group and noted that CL0P branding alone is insufficient for attribution.
Oracle issued a security alert for CVE-2025-61882 on 4 October 2025. The alert described unauthenticated remote exploitation risk, published observed indicators, and urged customers to apply updates as soon as possible.
That case shows that serious Oracle product vulnerabilities have led to real data theft, and that Oracle has responded with targeted alerts and patches. It does not establish that the same actors, techniques, or indicators apply to CVE-2026-114847, and it should not be read as attribution for this AHF issue.
References
- NVD: CVE-2026-114847
- CVE record for CVE-2026-114847 (CVE Services API)
- Oracle Critical Security Patch Update Advisory, November 2026
- Oracle CSPU November 2026 CSAF advisory (JSON)
- Text Form of Oracle CSPU November 2026 Risk Matrices
- My Oracle Support Patch Availability Document CPU431
- Patching Oracle Autonomous Health Framework
- Installing, Upgrading, Patching, Downgrading, and Uninstalling Oracle Autonomous Health Framework
- Running AHFCTL Upgrade Commands
- Installing Oracle Autonomous Health Framework
- Oracle Autonomous Health Framework Overview
- Oracle Autonomous Health Framework (AHF) FAQ
- Oracle Security Fixing Policies
- CWE 284: Improper Access Control
- FIRST CVSS v3.1 Specification Document
- CISA Known Exploited Vulnerabilities Catalog
- CISA KEV JSON feed
- Oracle Security Alert for CVE-2025-61882
- Google Threat Intelligence: Oracle EBS zero day exploited in extortion campaign
- About Oracle
- Oracle: Gartner Magic Quadrant for Cloud Database Management Systems
- StackFlag entry for CVE-2026-114847
- infrastack.ai entry for CVE-2026-114847
- VulDB entry for CVE-2026-114847



