dbcve.org
Financial Services Analytical Applications InfrastructureApplication · Oracle

CVE-2026-34313

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Financial Services Analytical Applications Infrastructure product of Oracle Financial Services Applications (component: Platform). Supported versions that are affected are 8.0.7.9, 8.0.8.7 and 8.1.2.5. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Financial Services Analytical Applications Infrastructure. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Financial Services Analytical Applications Infrastructure 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

Oracle Financial Services Analytical Applications Infrastructure contains a vulnerability in its Platform component that allows low-privileged attackers with network access via HTTP to access sensitive data. The CVSS vector indicates a confidentiality impact (C:H) with no integrity or availability effects, suggesting an information disclosure vulnerability such as broken access control or data exposure flaw.

MitigationApply the relevant Oracle Financial Services patch or upgrade to a supported version beyond 8.1.2.5 as specified in Oracle's Critical Patch Update documentation. Restrict network access to the Platform component and verify least-privilege access controls are enforced.

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
Financial Services Analytical Applications InfrastructureApplication
Affected:= 8.0.7.9.0= 8.0.8.7.0= 8.1.2.5.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 Financial Services Analytical Applications Infrastructure installation
    Look for OFSAAI installation directories, typically under $ORACLE_HOME or /u01/oracle/, and check for the presence of the Platform component files in the installation path
    Affected if OFSAAI is installed with the Platform component present
  2. Determine installed OFSAAI version
    Check the version file in the OFSAAI installation directory, commonly found in the installation root or VERSION.txt file within the installation
    Affected if The installed version matches exactly 8.0.7.9.0, 8.0.8.7.0, or 8.1.2.5.0
  3. Verify Platform component is enabled
    Check OFSAAI configuration files for Platform component enablement, typically in the web.xml or application-specific configuration under the OFSAAI home directory
    Affected if The Platform component is configured and active in the OFSAAI environment
  4. Assess network exposure of the Platform component
    Review network listener configurations and firewall rules to determine if the HTTP interface for the Platform component is accessible from untrusted networks
    Affected if The Platform component HTTP listener is exposed to network access beyond trusted boundaries
  5. Check access control configuration
    Review user privileges and role mappings in the OFSAAI security configuration to verify if low-privileged users can access sensitive data through the Platform component
    Affected if Low-privileged users have been granted access that could allow sensitive data retrieval via HTTP requests

A user is affected if Oracle Financial Services Analytical Applications Infrastructure version 8.0.7.9.0, 8.0.8.7.0, or 8.1.2.5.0 is installed with the Platform component enabled and accessible over HTTP.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Oracle Financial Services patch or upgrade to a supported version beyond 8.1.2.5 as specified in Oracle's Critical Patch Update documentation. Restrict network access to the Platform component and verify least-privilege access controls are enforced.

Fix this in Financial Services Analytical Applications Infrastructure Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34313 — 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-34313 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