CVE-2026-46937
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 iSetup product of Oracle E-Business Suite (component: General Ledger Update Transform, Reports). 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 iSetup. Successful attacks of this vulnerability can result in takeover of Oracle iSetup. 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 · high confidenceVulnerability in Oracle iSetup General Ledger Update Transform/Reports component allowing low-privileged attackers with network access via HTTP to achieve complete takeover of Oracle iSetup. Easily exploitable with high confidentiality, integrity, and availability impacts.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Oracle iSetup is installedLocate Oracle E-Business Suite installation directories (typically under $APPL_TOP or Oracle E-Business Suite home) and verify iSetup module presence. Check for iSetup related directories, war files, or Oracle Applications Manager (OAM) recognition of the module.Affected if Oracle iSetup is not installed or the module directory is absent from the E-Business Suite environment.
-
Identify Oracle iSetup versionQuery the Oracle E-Business Suite version using Oracle Applications Manager, or run SQL query against FND_PRODUCT_GROUPS table: SELECT patch_level FROM fnd_product_groups WHERE product='IZU' (iSetup product code). Alternatively, check the Oracle iSetup about page via the web interface if accessible.Affected if Unable to determine version or iSetup is not recognized as a registered product.
-
Compare installed version to affected rangeVerify if the identified version falls within >= 12.2.3 and <= 12.2.15. Document the exact version number for comparison.Affected if Installed version is between 12.2.3 and 12.2.15 inclusive.
-
Check if General Ledger Update Transform/Reports component is accessibleIdentify if the General Ledger Update Transform/Reports functionality within iSetup is exposed and accessible via HTTP. Review iSetup responsibility menus and concurrent program definitions to locate this specific component.Affected if The General Ledger Update Transform/Reports component exists and is accessible to low-privileged users through iSetup responsibilities.
-
Assess network exposure of iSetup interfacesReview network accessibility of Oracle iSetup web interfaces. Determine if iSetup servlets and reports are exposed to untrusted networks or if HTTP access is limited to trusted internal networks only.Affected if iSetup interfaces are reachable over network accessible ports (typically 8000-8090) from untrusted networks or the internet.
The environment is affected if Oracle iSetup is installed with version 12.2.3 through 12.2.15, the General Ledger Update Transform/Reports component is accessible, and the iSetup interface is reachable over the network to potential attackers.
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 Update for affected Oracle E-Business Suite versions 12.2.3-12.2.15. Until patched, restrict network access to Oracle iSetup interfaces and implement Oracle's E-Business Suite security best practices.
- Consultation8.0 h
- Implementation16.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46937 — 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-46937 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