dbcve.org
Flexcube Universal BankingApplication · Oracle

CVE-2026-21978

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-20
Fix available
A fix is available. Upgrade to after 14.8.0.0.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

SQL injection or improper authorization vulnerability in Oracle FLEXCUBE Universal Banking's Relationship Pricing component allows authenticated low-privileged users to access sensitive banking data via crafted HTTP requests. The CVSS vector indicates confidentiality impact (C:H) with no integrity or availability impact, suggesting data exfiltration rather than modification.

MitigationApply Oracle Critical Patch Update for affected versions (14.0.0.0.0-14.8.0.0.0). Additionally, restrict network access to Relationship Pricing interfaces and enforce least-privilege user access controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Flexcube Universal BankingApplication
Affected:>= 14.0.0, <= 14.8.0.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle FLEXCUBE Universal Banking installation
    Locate the FLEXCUBE installation directory and check for existence of flexcube-related executables, libraries, or configuration files. Common paths may include Oracle middleware home directories or application servers hosting the banking system.
    Affected if Oracle FLEXCUBE Universal Banking software is present on the system
  2. Determine installed FLEXCUBE version
    Access the FLEXCUBE administration console, check version information in the about section, or inspect version files in the installation directory. Compare the version number against the affected range 14.0.0.0.0 to 14.8.0.0.0.
    Affected if Installed version falls within >= 14.0.0 and <= 14.8.0.0.0
  3. Verify Relationship Pricing component is enabled
    Check FLEXCUBE configuration files or administration panel to confirm whether the Relationship Pricing module/component is deployed and active. Look for configuration entries referencing 'Relationship Pricing' or 'RPR' module.
    Affected if Relationship Pricing component is deployed and accessible in the application
  4. Inspect network accessibility of pricing interfaces
    Review network configuration, firewall rules, or web server access controls to determine if the Relationship Pricing HTTP endpoints are exposed beyond the internal network or to untrusted users.
    Affected if Relationship Pricing HTTP interfaces are accessible from less-trusted networks or external endpoints
  5. Audit user access controls for low-privileged accounts
    Review user role assignments and privilege levels in the FLEXCUBE user management system. Check if low-privileged or unprivileged users have any access to the Relationship Pricing functionality.
    Affected if Low-privileged or unauthorized user accounts can access or query Relationship Pricing data

The environment is affected if Oracle FLEXCUBE Universal Banking version 14.0.0 through 14.8.0.0.0 is installed with the Relationship Pricing component enabled and accessible to authenticated low-privileged users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 14.8.0.0.0
Interim mitigation

Apply Oracle Critical Patch Update for affected versions (14.0.0.0.0-14.8.0.0.0). Additionally, restrict network access to Relationship Pricing interfaces and enforce least-privilege user access controls.

Fix this in Flexcube Universal Banking Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,232.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21978 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-21978 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data