CVE-2026-46958
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 Subledger Accounting product of Oracle E-Business Suite (component: Internal Operations). Supported versions that are affected are 12.2.3-12.2.15. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Subledger Accounting. Successful attacks of this vulnerability can result in takeover of Oracle Subledger Accounting. CVSS 3.1 Base Score 7.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/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 confidenceVulnerability in Oracle Subledger Accounting (part of Oracle E-Business Suite) allows low privileged attackers with network access via HTTP to potentially take complete control of the affected module. The component affected is Internal Operations, and all confidentiality, integrity, and availability impacts are rated HIGH.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Identify Oracle EBS versionQuery the Oracle Applications version using SQL: SELECT release_name FROM apps.fnd_product_groups; or check the environment variable $APPL_TOP or the adident utility output for the Oracle Application version file.Affected if The version returned is between 12.2.3 and 12.2.15 inclusive
-
Verify Subledger Accounting module is installedQuery the Oracle EBS module status: SELECT application_id, application_name FROM fnd_application WHERE application_name LIKE '%Subledger Accounting%'; or check via Oracle Applications Manager (OAM) interface.Affected if The Subledger Accounting module is present in the system
-
Confirm Internal Operations component is accessibleCheck user access to the Internal Operations component within Subledger Accounting. Query: SELECT responsibility_id, responsibility_name FROM fnd_responsibility WHERE responsibility_name LIKE '%Internal Operations%'; or verify through EBS responsibility assignments.Affected if Users with low privileges have access to the Internal Operations functionality via web (HTTP) interface
-
Verify HTTP access is enabledConfirm the Oracle EBS web entry points are active. Check that the OA_HTML or equivalent web listener is running and accessible: Verify port configuration in $CONTEXT_FILE and confirm the web tier is responding.Affected if The EBS web interface (HTTP/HTTPS) is exposed and operational
You are affected if your Oracle E-Business Suite version is 12.2.3 through 12.2.15 AND the Subledger Accounting module with Internal Operations component is installed and accessible via HTTP to low-privileged users.
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 the relevant Oracle Critical Patch Update (CPU) for Oracle E-Business Suite addressing CVE-2026-46958. Given this is an EBS module, ensure thorough testing in a non-production environment before production deployment due to potential integration impacts.
- Consultation6.0 h
- Implementation10.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 $8,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46958 — 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-46958 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