CVE-2026-46949
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 unauthenticated attacker with network access via HTTP to compromise Oracle Advanced Outbound Telephony. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Advanced Outbound Telephony accessible data as well as unauthorized access to critical data or complete access to all Oracle Advanced Outbound Telephony accessible data. CVSS 3.1 Base Score 9.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).
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 confidenceUnauthenticated HTTP vulnerability in Oracle Advanced Outbound Telephony Internal Operations component allows remote attackers to create, delete, or modify critical data and gain complete access to all accessible data due to missing authentication controls on network-accessible HTTP endpoints.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 database or check the Oracle Applications context file (usually at $INST_TOP/ora/10.1.2/appsutil/install/ - or use Oracle Applications Manager) to determine if Oracle E-Business Suite version falls within 12.2.3 to 12.2.15Affected if The installed Oracle EBS version is between 12.2.3 and 12.2.15 inclusive
-
Confirm Advanced Outbound Telephony componentVerify the Oracle Advanced Outbound Telephony module is installed by checking the Oracle EBS modules list via Oracle Applications Manager or by querying FND_PRODUCT_INSTALLATIONS tableAffected if Advanced Outbound Telephony component is present in the installation
-
Check Internal Operations HTTP exposureAttempt to access the Internal Operations HTTP endpoints (typically under /OA_HTML/ or /oa_servlets/ related to outbound telephony) without providing credentials using a web browser or curl commandAffected if The Internal Operations component endpoints are reachable via HTTP without requiring authentication
-
Verify network accessibilityDetermine if the Oracle EBS HTTP interfaces are exposed to untrusted networks by reviewing firewall rules, load balancer configurations, or WAF policies that protect the EBS web endpointsAffected if The EBS HTTP ports (typically 8000-8009 or similar) are accessible from untrusted network segments or the internet
You are affected if your Oracle EBS version is 12.2.3 through 12.2.15, the Advanced Outbound Telephony component is installed, and its Internal Operations HTTP endpoints are accessible without authentication from a network where attackers could reach them.
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 · scopedApply Oracle Critical Patch Update addressing CVE-2026-46949 for E-Business Suite 12.2.3-12.2.15; until patched, restrict network access to Oracle EBS HTTP interfaces via firewall or WAF.
Oracle E-Business Suite 12.2.16 or later (obtain specific CPU patch from Oracle)
- Contact Oracle Support to obtain the latest Critical Patch Update (CPU) for Oracle E-Business Suite that addresses CVE-2026-46949
- Apply the CPU patch following Oracle's standard patch application process for E-Business Suite
- After patching, verify the fix by confirming that the Internal Operations component no longer allows unauthenticated access
- Test that Oracle Advanced Outbound Telephony functionality remains intact after the patch
Generated from the published advisory — verify against the referenced sources before acting.
- 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-46949 — 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-46949 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