CVE-2026-34320
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 Customer Screening product of Oracle Financial Services Applications (component: User Interface). The supported version that is affected is 8.1.2.8.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Financial Services Customer Screening. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Financial Services Customer Screening accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/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 confidenceUnauthenticated HTTP vulnerability in the User Interface component of Oracle Financial Services Customer Screening version 8.1.2.8.0 allows remote attackers to gain unauthorized access to sensitive data via network requests without any credentials. The CVSS vector indicates a network-based attack with low complexity, no user interaction required, resulting in high confidentiality impact.
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.1.2.8.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle Financial Services Customer Screening installationLocate the OFSAA (Oracle Financial Services Analytical Applications) installation directory, typically under $ORACLE_HOME or /opt/oracle, and check for the Customer Screening module folder or check the application startup scripts for 'CustomerScreening' or 'CS' module references.Affected if The Oracle Financial Services Customer Screening application is installed and running.
-
Verify installed version numberCheck the version of the Customer Screening component by inspecting the installation manifest, About page in the web interface, or the version file in the installation directory. Common locations: <install_dir>/ CustomerScreening/version.txt or the OFSAAI version.info file.Affected if The installed version is exactly 8.1.2.8.0.
-
Confirm HTTP interface is enabledCheck the web server configuration (OHS/Oracle HTTP Server or embedded JVM) for the Customer Screening application. Look for the context path typically used by Customer Screening (often /ofscaa/CS or similar) in the deployed ear/war files or in the web.xml descriptor.Affected if The Customer Screening User Interface component is deployed and accessible via HTTP/HTTPS.
-
Assess network exposureReview firewall rules, load balancer configurations, or network ACLs to determine if the Customer Screening web interface is accessible from untrusted networks. Check if the application port (commonly 8080, 8443, or the configured OFSAAI port) is exposed to the internet or untrusted VLANs.Affected if The Customer Screening HTTP interface is reachable from network segments outside the trusted internal network.
A user is affected if Oracle Financial Services Customer Screening version 8.1.2.8.0 is installed with its User Interface component exposed to network access.
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's available security patches for this vulnerability. As an interim measure, restrict network access to the Customer Screening application through network segmentation and consider deploying a WAF to filter malicious HTTP requests.
- 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-34320 — 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-34320 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