dbcve.org
Weblogic ServerApplication · Oracle

CVE-2026-46848

HIGH · 7.9 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
79/100
Remediation priority · High

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 WebLogic Server product of Oracle Fusion Middleware (component: Console). Supported versions that are affected are 14.1.2.0.0 and 15.1.1.0.0. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where WebLogic Server executes to compromise WebLogic Server. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in WebLogic Server, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all WebLogic Server accessible data as well as unauthorized access to critical data or complete access to all WebLogic Server accessible data. CVSS 3.1 Base Score 7.9 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/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 confidence

This is a local privilege escalation and data modification vulnerability in Oracle WebLogic Server's Console component. A low-privileged user with local system access can exploit the flaw, combined with social engineering (requiring human interaction from another user), to gain unauthorized read/write access to WebLogic Server data and potentially impact additional products in the environment due to scope change.

MitigationApply Oracle's published security patches for the affected WebLogic Server versions (14.1.2.0.0 and 15.1.1.0.0). Restrict local access to the infrastructure and educate users about social engineering risks to mitigate the human interaction requirement.

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
Weblogic ServerApplication
Affected:= 14.1.2.0.0= 15.1.1.0.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
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify WebLogic Server installation and version
    Locate the WebLogic Server installation directory and check the version file or use the WebLogic administration tool to query the installed version. Common locations include the Oracle middleware home directory. Use 'java -jar wlserver_14.1.2.0.0/bin/wlst.sh -help' or check version manifest files in the installation directory.
    Affected if The installed version is exactly 14.1.2.0.0 or exactly 15.1.1.0.0
  2. Verify Console component is enabled
    Check the WebLogic Server configuration for the Administration Console. This is typically accessible via HTTP/HTTPS on the console port (default 7001). Verify the console application is deployed and accessible by attempting to reach the console URL or checking config.xml for console deployment status.
    Affected if The WebLogic Console is deployed and accessible on the affected versions (14.1.2.0.0 or 15.1.1.0.0)
  3. Review local user access controls
    Examine the WebLogic Server security realm and embedded LDAP configuration to identify low-privileged accounts that have local system access. Check OS-level user permissions on the server host.
    Affected if There are low-privileged WebLogic users or local OS users with console access who should not have elevated privileges
  4. Check for social engineering attack vectors
    Review recent administrative actions in the console audit logs and examine whether low-privileged users can initiate actions requiring administrator confirmation. Look for patterns of cross-user interaction requests.
    Affected if The console allows actions that require human interaction between different privilege levels, enabling social engineering exploits

A user is affected if they are running exactly WebLogic Server version 14.1.2.0.0 or 15.1.1.0.0 with the Console component enabled and have low-privileged users who could be targeted for social engineering.

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 Oracle's published security patches for the affected WebLogic Server versions (14.1.2.0.0 and 15.1.1.0.0). Restrict local access to the infrastructure and educate users about social engineering risks to mitigate the human interaction requirement.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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 locally
dbcve dependency scanner

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