VulnerabilityPublished 20 Jan 2026

CVE-2026-21973: Oracle FLEXCUBE Investor Servicing · Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to

Affects Oracle FLEXCUBE Investor ServicingSource CVE Database V5

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Oracle CorporationOracle FLEXCUBE Investor Servicing	Affected =14.5.0.15.0 =14.7.0.8.0 =14.8.0.1.0	Fixed in–
Mavencom.oracle/flexcube-investor-servicing`pkg:maven/com.oracle/flexcube-investor-servicing`Other threats	Affected =14.5.0.15.0 =14.7.0.8.0 =14.8.0.1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Apply Oracle's security patches for FLEXCUBE Investor Servicing immediately once available, as patching is the most effective mitigation. 2. Restrict network access to the FLEXCUBE Investor Servicing application using network segmentation and firewalls, limiting HTTP access only to trusted internal networks or VPNs. 3. Implement strict access controls and monitor user privileges to ensure that low-privileged accounts cannot be leveraged for exploitation. 4. Enable detailed logging and continuous monitoring of FLEXCUBE systems to detect unusual data access or modification patterns indicative of exploitation attempts. 5. Conduct regular security assessments and penetration testing focused on the Security Management System component to identify and remediate potential weaknesses. 6. Educate system administrators and security teams about this vulnerability and the importance of rapid response. 7. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block suspicious HTTP requests targeting FLEXCUBE. 8. Review and harden configuration settings related to authentication and authorization within FLEXCUBE to minimize attack surface.

Description

Vulnerability in the Oracle FLEXCUBE Investor Servicing product of Oracle Financial Services Applications (component: Security Management System). Supported versions that are affected are 14.5.0.15.0, 14.7.0.8.0 and 14.8.0.1.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle FLEXCUBE Investor Servicing. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle FLEXCUBE Investor Servicing accessible data as well as unauthorized access to critical data or complete access to all Oracle FLEXCUBE Investor Servicing accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).

Impact

For European organizations, particularly banks and financial institutions using Oracle FLEXCUBE Investor Servicing, this vulnerability poses a substantial risk. The unauthorized modification or access to critical investor servicing data could lead to financial fraud, loss of customer trust, regulatory penalties under GDPR and other financial regulations, and operational disruptions. Confidentiality breaches could expose sensitive investor information, while integrity compromises could result in manipulated financial records or transactions. The lack of availability impact means systems may remain operational, potentially masking ongoing data manipulation. Given the interconnected nature of financial services in Europe, a successful attack could have cascading effects across multiple institutions and markets. Additionally, regulatory scrutiny in Europe is stringent, so exploitation could lead to significant legal and compliance consequences.

References

oracle.com/security-alerts/cpujan2026.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Jan 2026, 22:24 UTC

Technical details

References

Community reviews

Related threats