CVE-2026-46899
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 Enterprise Command Center Framework product of Oracle E-Business Suite (component: Core). Supported versions that are affected are V15 and V16. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Enterprise Command Center Framework. While the vulnerability is in Oracle Enterprise Command Center Framework, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Enterprise Command Center Framework accessible data as well as unauthorized access to critical data or complete access to all Oracle Enterprise Command Center Framework accessible data. CVSS 3.1 Base Score 9.6 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 · moderate confidenceThis is an unauthenticated HTTP-based vulnerability in the Core component of Oracle Enterprise Command Center Framework (ECCF) versions V15 and V16. A low-privileged attacker with network access can exploit this flaw to create, delete, or modify critical data within ECCF, as well as gain unauthorized read access to sensitive or all accessible data. The scope change indicates the attack may impact additional Oracle products beyond ECCF.
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= 15= 16CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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.
-
Verify Oracle Enterprise Command Center Framework is installedQuery the Oracle E-Business Suite application registry or use Oracle Application Object Library (FND_PRODUCT_INSTALLATIONS) to identify if the Enterprise Command Center Framework component is present in your environment.Affected if The Enterprise Command Center Framework component is found in the product installations table.
-
Determine the installed version of Enterprise Command Center FrameworkQuery the Oracle EBS version information for the Enterprise Command Center Framework specifically. This may be found in FND_PRODUCT_GROUPS, FND_RELEASES, or the specific ECC framework tables that store the framework version.Affected if The version returned is exactly 15 or exactly 16 (the affected versions per the CVE).
-
Confirm HTTP access to Oracle E-Business Suite is enabledCheck the Oracle E-Business Suite listener configuration (either Oracle HTTP Server or Oracle Web Listener) to verify that the /ecc/ or Enterprise Command Center endpoints are accessible via HTTP or HTTPS.Affected if The HTTP listener is active and the ECC framework endpoints are accessible over the network.
-
Review user access privileges to the Command CenterQuery Oracle EBS responsibility and role assignments (FND_USER, FND_RESPONSIBILITY, FND_USER_RESPONSIBILITIES) to determine which users have access to Enterprise Command Center Framework privileges and responsibilities.Affected if Low-privileged users or roles with minimal restrictions are assigned access to the ECC framework.
-
Check for unauthorized data access or modification indicatorsReview Oracle audit logs, FND_LOG_MESSAGES, and ECC-specific audit trails for any unexpected CREATE, DELETE, or UPDATE operations on critical data within the framework that occurred outside normal administrative workflows.Affected if Unexpected or unauthorized data modification events are present in the audit logs.
Your environment is affected if Oracle Enterprise Command Center Framework versions 15 or 16 are installed, the HTTP interface is accessible, and low-privileged users can access the framework.
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's published security patches for Oracle E-Business Suite addressing this vulnerability in ECCF. Restrict network exposure of HTTP interfaces to ECCF as an interim control until patching can be completed.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46899 — 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-46899 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