CVE-2026-62632: Vulnerability in the Oracle Reports Developer product of Oracle Fusion Middleware (component: Security and...
Vulnerability in the Oracle Reports Developer product of Oracle Fusion Middleware (component: Security and Authentication). The supported version that is affected is 14.1.2.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Reports Developer. Successful attacks of this vulnerability can result in takeover of Oracle Reports Developer. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
Security readout for executives and security teams
Plain-English summary
An unauthenticated attacker who can reach Oracle Reports Developer over HTTP may take complete control of the application. Oracle identifies supported version 14.1.2.0.0 as affected. Because exploitation requires no credentials or user interaction and can affect confidentiality, integrity, and availability, reachable deployments warrant urgent attention.
Executive priority
Treat affected, network-reachable systems as an immediate remediation priority. Complete exposure identification and containment promptly, then apply and verify Oracle’s prescribed remediation. Systems reachable from the internet or broadly accessible internal networks should receive the highest priority because compromise could enable full application takeover and major data or service impact.
Technical view
CVE-2026-62632 is an access-control vulnerability (CWE-284) in Oracle Reports Developer’s Security and Authentication component. It is network-exploitable over HTTP with low complexity, no privileges, and no user interaction. Successful exploitation can cause application takeover. The assigned CVSS 3.1 score is 9.8 with high confidentiality, integrity, and availability impacts.
Likely exposure
Exposure is most likely where Oracle Reports Developer 14.1.2.0.0 accepts HTTP connections from untrusted networks. Internet-facing systems are especially concerning, but an internally reachable deployment could also be attacked by a compromised host or unauthorized internal user. The supplied sources do not identify other affected versions.
Exploitation context
The CVE is not listed as CISA KEV in the supplied bundle, and no cited source establishes active exploitation. This does not prove exploitation is absent. Publicly supplied evidence establishes an easily exploitable, unauthenticated HTTP attack path, but provides no exploit-method or observed-campaign details.
Researcher notes
The public bundle identifies the vulnerable component, affected supported version, attack vector, impact, CWE, and CVSS vector. It does not provide root-cause detail, vulnerable endpoints, patch identifiers, indicators of compromise, or evidence of exploitation. Avoid assuming additional affected releases or a specific corrective version without consulting Oracle’s advisory.
Mitigation direction
Inventory Oracle Reports Developer deployments and identify systems running version 14.1.2.0.0.
Review the Oracle advisory for the vendor-prescribed patch or remediation and apply it urgently.
Restrict HTTP access to trusted administrative or application networks until remediation is verified.
Increase monitoring for unexpected access, configuration changes, and anomalous activity affecting exposed deployments.
Validation and detection
Confirm deployed Oracle Reports Developer versions using authoritative asset and configuration records.
Verify whether HTTP endpoints are reachable from the internet or other untrusted network segments.
Confirm the Oracle-prescribed remediation is installed using vendor-supported version or patch evidence.
Review relevant logs for suspicious unauthenticated requests and unexpected administrative or application changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.