CVE-2026-34325
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 · uneditedVulnerability in the Oracle Financial Services Analytical Applications Infrastructure product of Oracle Financial Services Applications (component: User Interface). 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 logon to the infrastructure where Oracle Financial Services Analytical Applications Infrastructure executes to compromise Oracle Financial Services Analytical Applications Infrastructure. Successful attacks require human interaction from a person other than the attacker. 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 as well as unauthorized update, insert or delete access to some of Oracle Financial Services Analytical Applications Infrastructure accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Financial Services Analytical Applications Infrastructure. CVSS 3.1 Base Score 6.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:H).
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 confidenceVulnerability in Oracle Financial Services Analytical Applications Infrastructure User Interface component allows a low-privileged attacker with local logon access to compromise the system. Successful exploitation requires human interaction from a person other than the attacker and can result in unauthorized access to critical or all accessible data, unauthorized data modification/deletion, or denial of service through hangs or crashes.
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= 8.0.7.9.0= 8.0.8.7.0= 8.1.2.5.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed OFSAA Infrastructure versionLocate the OFSAA installation directory and check the version file (often VERSION.txt or manifest file in the installation root). Common paths include /opt/ofsaa, /u01/ofsaa, or the Windows equivalent under Program Files/Oracle. Alternatively, check the About section within the OFSAA User Interface application.Affected if The installed version matches exactly 8.0.7.9.0, 8.0.8.7.0, or 8.1.2.5.0
-
Verify User Interface component is deployedConfirm the OFSAA User Interface (OFSAAI UI) web application is deployed and accessible. Check the application server (WebLogic, WebSphere, or Tomcat) deployment status, or verify the ui war/ear file exists in the deployed applications directory.Affected if The User Interface component is deployed and running
-
Confirm local logon access is enabledReview the application authentication configuration to determine if local operating system users or database users can logon directly to the OFSAA system. Check authentication settings in the OFSAA configuration files (typically in the <OFSAA_HOME>/conf directory) or the application server security realm.Affected if Local user authentication is permitted (not using centralized SSO only)
-
Check for shared workstation or terminal accessAssess whether multiple users have access to the same workstation or terminal where the OFSAA UI is accessible, as the vulnerability requires human interaction from a person other than the attacker.Affected if Multiple users share access to systems running the OFSAA UI
You are affected if the installed Oracle Financial Services Analytical Applications Infrastructure version is exactly 8.0.7.9.0, 8.0.8.7.0, or 8.1.2.5.0 AND the User Interface component is deployed AND low-privileged local users can logon AND the UI is accessible to multiple users where human interaction could be exploited.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle security patches for versions 8.0.7.9, 8.0.8.7, and 8.1.2.5 when available. Until then, limit local access to the infrastructure and monitor for suspicious user activity.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34325 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34325 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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