CVE-2026-46950
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 Advanced Outbound Telephony 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 Advanced Outbound Telephony. Successful attacks of this vulnerability can result in takeover of Oracle Advanced Outbound Telephony. 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 confidenceA network-accessible HTTP vulnerability in Oracle Advanced Outbound Telephony (Internal Operations component) affecting versions 12.2.3-12.2.15. Exploitable by low-privileged attackers with network access, allowing complete takeover (full compromise of confidentiality, integrity, and availability) via the web interface.
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.
-
Identify Oracle Advanced Outbound Telephony versionQuery the Oracle E-Business Suite version information for the Advanced Outbound Telephony module. This is typically available through the Oracle Applications Manager (OAM) interface or by querying the FND_PRODUCT_INSTALLATIONS or APPS.MWA system tables if you have database access.Affected if The installed version is 12.2.3 through 12.2.15 inclusive.
-
Confirm Internal Operations component is in useCheck the Oracle Advanced Outbound Telephony configuration to determine if the Internal Operations sub-component is enabled or configured. This may be visible in the Telephony Manager administrative console or through the MWA_PRIVATE.ADMIN_CONFIG package if accessible.Affected if Internal Operations component is actively configured or enabled in the Telephony installation.
-
Verify HTTP network exposureReview network accessibility of the Oracle E-Business Suite application servers. Determine if the Oracle HTTP Server ports or web entry points for the Advanced Outbound Telephony module are exposed to untrusted networks (not behind proper authentication gateways or VPNs).Affected if The Oracle E-Business Suite web interfaces for Advanced Outbound Telephony are reachable over HTTP/HTTPS from low-privileged network users or untrusted networks.
-
Check for existing patchesReview the Oracle E-Business Suite patch history to see if the specific CPU patch addressing CVE-2026-46950 has been applied. This can be checked via Oracle Patch Advisor or by querying the AD_PATCHES table in the APPS schema.Affected if The CVE-2026-46950 specific patch has NOT been applied to the Oracle Advanced Outbound Telephony installation.
You are affected if Oracle Advanced Outbound Telephony version 12.2.3-12.2.15 is installed, the Internal Operations component is enabled, and the HTTP interface is accessible to low-privileged users without the CVE-2026-46950 patch applied.
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 Oracle Critical Patch Update addressing CVE-2026-46950 for Oracle E-Business Suite 12.2.3-12.2.15. If no patch is available, restrict network access to the Internal Operations component via firewall or access controls and monitor for exploitation indicators.
- Consultation4.0 h
- Implementation8.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46950 — 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-46950 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