Skip to main content

CVE-2026-114841Oracle Financial Services Regulatory Reporting vulnerability

Low priorityMedium5.5EPSS not scored yet

CVE-2026-114841 is a vulnerability in Oracle Financial Services Regulatory Reporting, rated medium (5.5 on CVSS 3.1).

Why this priority: Medium severity, with no exploitation signal.

Published · Updated · NVD status: Received

What it is

The record does not classify the weakness yet; the description below says what the reporter found.

How it is reached

An attacker can exploit it by someone who can already run code or sign in on the machine, with an ordinary user account, and nobody has to click anything.

What an attacker gains

A successful attack can read the data it protects.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. No fixed version is listed yet. Find every place Oracle Financial Services Regulatory Reporting runs, watch the references for a fix, and plan a replacement if it is no longer supported.
  2. Limit who can run code or sign in on the hosts that run it.

Description from NVD

Vulnerability in the Oracle Financial Services Regulatory Reporting product of Oracle Financial Services Applications (component: Internal Operations). The supported version that is affected is 8.1.2.10. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Financial Services Regulatory Reporting executes to compromise Oracle Financial Services Regulatory Reporting. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Financial Services Regulatory Reporting accessible data. CVSS 3.1 Base Score 5.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Oracle Financial Services Regulatory Reporting. Start from where it runs and what it is connected to.

Trust boundaries in play

  • Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.

Questions to answer about your own systems

  • Where does Oracle Financial Services Regulatory Reporting run in your systems, and at which version?
  • Which of those hosts also run code or users you do not fully trust?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.