dbcve.org
Project Portfolio AnalysisApplication · Oracle

CVE-2026-46961

HIGH · 8.8 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to after 12.2.15 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 Oracle Project Portfolio Analysis product of Oracle E-Business Suite (component: Internal Operations). Supported versions that are affected are 12.2.3-12.2.15. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Project Portfolio Analysis. Successful attacks of this vulnerability can result in takeover of Oracle Project Portfolio Analysis. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 confidence

A high-severity vulnerability in Oracle Project Portfolio Analysis (Internal Operations component) allows low-privileged attackers with network access via HTTP to achieve complete system compromise (takeover). The flaw affects versions 12.2.3 through 12.2.15 of the Oracle E-Business Suite module. The specific vulnerability type is not detailed, but the easily exploitable nature and full impact on confidentiality, integrity, and availability indicate a critical authentication or access control weakness.

MitigationApply Oracle's relevant Critical Patch Update (CPU) for this vulnerability to the Oracle E-Business Suite environment, or upgrade to a patched version beyond 12.2.15. Restrict network exposure of the HTTP interface to reduce attack surface until the patch can be applied.

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
Project Portfolio AnalysisApplication
Affected:>= 12.2.3, <= 12.2.15

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Identify Oracle E-Business Suite installation
    Locate the Oracle E-Business Suite installation directory and check the version file or query the database for the release version (FND_PRODUCT_GROUPS or similar metadata tables).
    Affected if The installed version falls within 12.2.3 through 12.2.15 inclusive.
  2. Verify Project Portfolio Analysis module is present
    Query the installed modules or check the Oracle Applications Manager (OAM) interface to confirm that the Project Portfolio Analysis component is installed and registered.
    Affected if The Project Portfolio Analysis module is present in the E-Business Suite installation.
  3. Confirm HTTP interface accessibility
    Check the Oracle HTTP Server (OHS) configuration or web tier settings to determine if the /OA_HTML/ or servlet pathways for Project Portfolio Analysis are accessible over HTTP/HTTPS from the network.
    Affected if The HTTP interface is exposed to network (non-localhost) access.
  4. Check Internal Operations component status
    Review the module configuration in Oracle Applications Manager or check the enabled responsibilities to determine if the Internal Operations component of Project Portfolio Analysis is enabled.
    Affected if The Internal Operations component is enabled in the configuration.
  5. Review access control configuration
    Examine the role assignments and permissions granted to low-privileged users, specifically looking at whether standard users can access the Project Portfolio Analysis functionality via HTTP.
    Affected if Low-privileged (non-admin) users have HTTP-accessible paths to the vulnerable component.

A user is affected if they have Oracle E-Business Suite version 12.2.3 to 12.2.15 with Project Portfolio Analysis and its Internal Operations component enabled, and the HTTP interface is network-accessible to low-privileged users.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 12.2.15
Interim mitigation

Apply Oracle's relevant Critical Patch Update (CPU) for this vulnerability to the Oracle E-Business Suite environment, or upgrade to a patched version beyond 12.2.15. Restrict network exposure of the HTTP interface to reduce attack surface until the patch can be applied.

Recommended fix Moderate confidence

Apply Oracle E-Business Suite Critical Patch Update containing fix for CVE-2026-46961 (contact Oracle Support for specific CPU version)

  1. Contact Oracle Support to obtain the Critical Patch Update (CPU) that addresses CVE-2026-46961 for Oracle E-Business Suite
  2. Request the latest Oracle E-Business Suite 12.2.15.x CPU patch for the Project Portfolio Analysis component
  3. Apply the security patch following Oracle's standard patching procedures for E-Business Suite
  4. After patching, verify the fix by reviewing the Oracle Critical Patch Update documentation for the applied version
  5. Confirm the Internal Operations module functionality remains intact after applying the security update
Caveat Oracle CPU patches are cumulative and may include other fixes; test thoroughly in a non-production environment before applying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Project Portfolio Analysis Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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