CVE-2026-35252
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 Security Service product of Oracle Fusion Middleware (component: C Oracle SSL API). Supported versions that are affected are 12.2.1.4.0 and 12.1.3.0.0. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTPS to compromise Oracle Security Service. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Security Service accessible data as well as unauthorized access to critical data or complete access to all Oracle Security Service accessible data. CVSS 3.1 Base Score 6.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/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 confidenceVulnerability in Oracle Security Service (C Oracle SSL API component) affecting versions 12.2.1.4.0 and 12.1.3.0.0 of Oracle Fusion Middleware. Difficult to exploit flaw allows low-privileged attacker with network access via HTTPS to compromise the service, requiring human interaction. Successful exploitation enables unauthorized creation, deletion, or modification of critical data, plus unauthorized access to critical or all accessible data (high confidentiality and integrity impacts, no availability 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= 12.1.3.0.0= 12.2.1.4.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
- High
- Privileges
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/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 Fusion Middleware installationLocate Oracle Fusion Middleware installation directory (typically ORACLE_HOME). Check for presence of Fusion Middleware software using inventory files (e.g., $ORACLE_HOME/oracle_common/modules/oracle.security.pki.jar) or Oracle Inventory (oraInventory).Affected if Oracle Fusion Middleware is not installed - not affected. If installed, proceed to version check.
-
Verify affected version numbersRun version check command or inspect version files in the Oracle Fusion Middleware installation. Common methods: check opatch lsinventory output, or read version.info/oracle_common/modules/version file, or query Oracle Enterprise Manager for middleware version.Affected if Installed version is EXACTLY 12.1.3.0.0 or EXACTLY 12.2.1.4.0 - potentially affected. Versions outside this exact match are not affected.
-
Confirm Oracle Security Service component presenceIdentify if the Oracle Security Service (C Oracle SSL API) component is installed and in use. Check for presence of SSL API libraries in oracle_common/modules or look for Java Security Service configurations in config files.Affected if Oracle Security Service / C Oracle SSL API component is not present - likely not affected. If present and version matches, proceed to network exposure check.
-
Check network exposure of SSL/TLS interfacesReview network listener configuration (Oracle HTTP Server, Oracle WebLogic Server) to determine if Oracle Security Service interfaces are exposed to network via HTTPS. Check listener ports and virtual host configurations.Affected if Service is network-accessible via HTTPS to untrusted users - exploitation possible. If only accessible locally or from trusted networks, exploitability is reduced.
User is affected only if Oracle Fusion Middleware is installed with an exact version of 12.1.3.0.0 or 12.2.1.4.0, the Oracle Security Service (C Oracle SSL API) component is present, and the service is network-accessible via HTTPS to potentially untrusted users.
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 Critical Patch Updates when released for this vulnerability. Until a patch is available, minimize network exposure of Oracle Security Service interfaces, enforce strict access controls, and monitor for suspicious SSL/TLS traffic patterns.
- 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-35252 — 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-35252 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