CVE-2026-21978VulnerabilityPublished 20 Jan 2026

CVE-2026-21978: Oracle FLEXCUBE Universal Banking · Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to

Affects Oracle FLEXCUBE Universal BankingSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% 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:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
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: None: There is no loss of integrity within 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 2026-10-26.

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 Universal Banking	Affected >=14.0.0.0.0 <=14.8.0.0.0	Fixed in–
Mavencom.oracle.flexcube/universal-banking`pkg:maven/com.oracle.flexcube/universal-banking`Other threats	Affected =14.0.0.0.0 <=14.8.0.0.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 official Oracle patches and updates for FLEXCUBE Universal Banking as soon as they become available to remediate the vulnerability. 2. Restrict network access to the FLEXCUBE application servers by implementing strict firewall rules and network segmentation, limiting HTTP access only to trusted internal networks or VPNs. 3. Employ strong authentication and authorization controls to minimize the privileges of users and services interacting with the Relationship Pricing component. 4. Monitor network traffic and application logs for unusual access patterns or attempts to exploit the vulnerability, using intrusion detection/prevention systems tailored to Oracle FLEXCUBE. 5. Conduct regular security assessments and penetration testing focused on the banking application to identify and remediate potential weaknesses. 6. Educate security and IT teams about this specific vulnerability and ensure incident response plans include scenarios involving unauthorized data access through application vulnerabilities. 7. Consider deploying web application firewalls (WAFs) with custom rules to detect and block exploitation attempts targeting this vulnerability.

Description

Vulnerability in the Oracle FLEXCUBE Universal Banking product of Oracle Financial Services Applications (component: Relationship Pricing). Supported versions that are affected are 14.0.0.0.0-14.8.0.0.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle FLEXCUBE Universal Banking. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle FLEXCUBE Universal Banking accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

Impact

For European organizations, particularly banks and financial institutions using Oracle FLEXCUBE Universal Banking, this vulnerability poses a significant risk to the confidentiality of sensitive financial data. Unauthorized access could lead to exposure of customer information, transaction details, and pricing data, potentially resulting in regulatory non-compliance, reputational damage, and financial losses. Given the critical role of banking infrastructure in the European economy, exploitation could undermine trust in financial services and disrupt business operations. Although the vulnerability does not affect data integrity or system availability, the confidentiality breach alone can have severe consequences under GDPR and other data protection regulations. The medium severity rating reflects the balance between ease of exploitation and the impact limited to confidentiality. However, the potential for lateral movement or further exploitation after initial access cannot be discounted, increasing the overall risk profile for affected organizations.

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:23 UTC

Technical details

References

Community reviews

Related threats