CVE-2026-46802
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 WebCenter Portal product of Oracle Fusion Middleware (component: Security Framework). Supported versions that are affected are 12.2.1.4.0 and 14.1.2.0.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle WebCenter Portal. While the vulnerability is in Oracle WebCenter Portal, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle WebCenter Portal. CVSS 3.1 Base Score 9.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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 confidenceA critical Security Framework vulnerability in Oracle WebCenter Portal (versions 12.2.1.4.0 and 14.1.2.0.0) allows low privileged attackers with network access via HTTP to achieve complete takeover of the portal. The CVSS 9.9 score reflects maximum impact across confidentiality, integrity, and availability with scope change allowing attacks to impact additional products beyond the directly affected component.
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.2.1.4.0= 14.1.2.0.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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/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 Oracle WebCenter Portal versionCheck the installed WebCenter Portal version by reviewing the Oracle inventory file at $ORACLE_HOME/oraInst.loc or by accessing the WebCenter Portal Administration console and navigating to the About/Version information pageAffected if The installed version is exactly 12.2.1.4.0 or exactly 14.1.2.0.0
-
Verify Security Framework component is in useCheck if WebCenter Portal's Security Framework is actively configured by reviewing the portal's web.xml deployment descriptor or by accessing the Security configuration in the WebCenter Portal Administration console under Security > Security ProvidersAffected if The Security Framework component is enabled and configured for the portal application
-
Confirm network accessibility of portal HTTP endpointsReview network configuration to determine if WebCenter Portal is accessible over HTTP/HTTPS from untrusted networks. Check load balancer, firewall, or reverse proxy rules that permit access to the portal's HTTP ports (typically 8888, 7001, or configured ports)Affected if The portal HTTP endpoints are reachable from untrusted or public networks without additional authentication barriers
-
Check for low-privileged user accountsReview the WebCenter Portal user directory (via Oracle Internet Directory, OID, or embedded LDAP) to confirm the presence of low-privileged user accounts that have network access to the portalAffected if Low-privileged user accounts exist and can authenticate to the portal over the network
If the installed version is exactly 12.2.1.4.0 or 14.1.2.0.0, the Security Framework is active, and the portal is network-accessible to untrusted sources with low-privileged accounts present, the environment is affected by this CVE.
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.
dbcve · scopedApply the latest Oracle Critical Patch Update (CPU) for Oracle WebCenter Portal addressing the Security Framework vulnerability; until patched, restrict network access to the portal to trusted users only and monitor for indicators of compromise.
Upgrade to the next available Oracle WebCenter Portal patch set that includes the fix for CVE-2026-46802 (consult Oracle Support for exact version)
- Check Oracle's official Critical Patch Update advisory for CVE-2026-46802 at oracle.com/security-alerts
- Identify the specific patch ID for WebCenter Portal from Oracle's patch database
- Apply the relevant security patch following Oracle's standard patch installation procedures
- Verify the patch was applied successfully by checking the WebCenter Portal version and security configuration
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46802 — 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-46802 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