CVE-2026-46945
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 iSupport 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 high privileged attacker with network access via HTTP to compromise Oracle iSupport. While the vulnerability is in Oracle iSupport, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle iSupport. CVSS 3.1 Base Score 9.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/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 vulnerability in Oracle iSupport's Internal Operations component (versions 12.2.3-12.2.15) allows a high privileged attacker with network access via HTTP to achieve complete system takeover. The CVSS 3.1 score of 9.1 reflects critical impact across confidentiality, integrity, and availability with a scope change indicating potential impact to additional Oracle products.
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.3, < 12.2.15CVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Confirm Oracle iSupport is installedQuery your Oracle E-Business Suite application server for the iSupport module. This can be done by checking the Oracle Applications manager console or by reviewing the installed Oracle E-Business Suite product list via adutl - or using the Oracle Application Manager web interface.Affected if Oracle iSupport is not installed in your environment, you are not affected by this vulnerability.
-
Determine the iSupport version numberLog into Oracle Application Manager or use the Oracle AD Utilities (adutl) to query the current version of the iSupport product. Navigate to the iSupport product information screen or run: 'adutl -product isuppt' to retrieve the version string.Affected if The version returned is blank, unlisted, or cannot be determined, requiring manual verification against Oracle documentation.
-
Compare version against affected rangeCompare the retrieved version to the affected range: 12.2.3 through 12.2.15. Any version greater than or equal to 12.2.3 and less than 12.2.15 falls within the affected range.Affected if Your installed version is 12.2.3, 12.2.4, 12.2.5, 12.2.6, 12.2.7, 12.2.8, 12.2.9, 12.2.10, 12.2.11, 12.2.12, 12.2.13, 12.2.14, or any 12.2.x version less than 12.2.15.
-
Verify iSupport Internal Operations component is accessibleCheck if the iSupport web interface is accessible by attempting to access the iSupport login page at your base URL path (typically /OA_HTML/ibE support.jsp or similar iSupport endpoints). Review your web server configuration to confirm iSupport servlets and pages are enabled.Affected if The iSupport web application is enabled and reachable, indicating the attack surface exists for this vulnerability.
-
Assess network exposure of iSupport interfacesReview firewall rules, load balancer configurations, and web server access controls to determine if the iSupport application is exposed to untrusted network segments. Check for any HTTP-accessible paths related to iSupport Internal Operations.Affected if iSupport is accessible over HTTP from networks outside your trusted internal zones, creating the conditions for remote exploitation described in the CVE.
You are affected if Oracle iSupport is installed and running any version from 12.2.3 up to (but not including) 12.2.15, with the iSupport web interface accessible over HTTP.
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 · scoped12.2.15
Apply Oracle's security patches for Oracle E-Business Suite iSupport as soon as they become available. Until then, restrict network access to iSupport interfaces to only trusted privileged users and monitor for anomalous administrative activities.
Oracle E-Business Suite 12.2.16 or latest 12.2.x release
- 1. Review the Oracle Critical Patch Update advisory for the relevant quarter addressing CVE-2026-46945
- 2. Obtain the latest Oracle iSupport patch from Oracle Support (My Oracle Support)
- 3. Apply the patch in a non-production environment first to validate compatibility
- 4. Create a full backup of the Oracle E-Business Suite database and application tier
- 5. Apply the patch during a planned maintenance window following Oracle's standard patching procedures
- 6. Verify the patch was applied successfully by checking the AD patch run history
- 7. Test critical iSupport workflows to ensure functionality is intact
- 8. Deploy to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46945 — 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-46945 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