CVE-2026-46952
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 Quality 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 Quality. Successful attacks of this vulnerability can result in takeover of Oracle Quality. 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 confidenceHTTP-based vulnerability in Oracle E-Business Suite's Quality module (Internal Operations component) affecting versions 12.2.3-12.2.15. Allows low-privileged authenticated attackers with network access to achieve full takeover of the Oracle Quality application due to 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 E-Business Suite installationQuery the Oracle database for the application version using SQL: SELECT release_name FROM apps.fnd_product_groups; or check the Oracle Applications Manager interface.Affected if E-Business Suite is installed and the release_name falls within 12.2.3 to 12.2.15.
-
Verify Oracle Quality module is enabledCheck if the Quality module is a registered responsibility in Oracle E-Business Suite by querying: SELECT * FROM fnd_responsibility WHERE responsibility_name LIKE '%Quality%'; or access the Quality module through the EBS Navigator.Affected if The Quality responsibility is available and accessible to users.
-
Confirm HTTP access to Oracle E-Business SuiteVerify that the Oracle E-Business Suite web interfaces (OA_HTML) are accessible over HTTP/HTTPS. Check the Oracle HTTP Server configuration or attempt to access the Quality module URL path (typically /OA_HTML/Quality).Affected if HTTP or HTTPS access to the E-Business Suite web interfaces is enabled and reachable over the network.
-
Check for low-privileged user accessReview user account assignments to determine if any non-admin users have access to the Quality module responsibility. Query: SELECT fr.responsibility_name, fu.user_name, fr.description FROM fnd_responsibility fr JOIN fnd_user_resp_groups fur ON fr.responsibility_id = fur.responsibility_id JOIN fnd_user fu ON fur.user_id = fu.user_id WHERE fr.responsibility_name LIKE '%Quality%';Affected if Any authenticated users with basic privileges (beyond just login) have access to the Quality module.
You are affected if Oracle E-Business Suite version 12.2.3 through 12.2.15 is installed, the Quality module is enabled and accessible via HTTP, and any authenticated users (including low-privileged ones) can access the network-accessible Quality application.
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-46952; if patch unavailable, restrict HTTP network access to Oracle E-Business Suite and enforce least-privilege user roles until remediation is possible.
Oracle E-Business Suite 12.2.16 or later (contact Oracle for exact fixed version)
- Contact Oracle Support to obtain the specific patch for CVE-2026-46952
- Request the latest Oracle E-Business Suite Critical Patch Update (CPU) that addresses this vulnerability
- Apply the patch following Oracle's standard patch application procedures for E-Business Suite
- After patching, verify the fix by testing the Oracle Quality Internal Operations functionality
- Confirm the patch was applied successfully by checking the Oracle applications version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46952 — 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-46952 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