CVE-2026-46916
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 Process Manufacturing Product Development product of Oracle E-Business Suite (component: Quality Management Specs). 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 Process Manufacturing Product Development. Successful attacks of this vulnerability can result in takeover of Oracle Process Manufacturing Product Development. 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 confidenceSQL injection or similar injection vulnerability in the Quality Management Specs component of Oracle Process Manufacturing Product Development (E-Business Suite) allows low-privileged authenticated attackers to execute arbitrary SQL commands via HTTP, leading to full system compromise including confidentiality, integrity, and availability.
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.
-
Verify Oracle E-Business Suite installationCheck if Oracle EBS is installed by looking for Oracle application processes (e.g., via ps aux | grep -i oracle or checking for $ORACLE_HOME/eBUS_APPS directory structure)Affected if Oracle EBS is not installed, this CVE does not apply
-
Confirm Oracle Process Manufacturing Product Development is in useIdentify if the Process Manufacturing Product Development module is installed. Check Oracle Applications Manager (OAM) or concurrent request outputs for product family 'Process Manufacturing'Affected if The Process Manufacturing Product Development component is not present, the vulnerability does not apply
-
Check the EBS version against affected rangeLog into Oracle EBS as a system administrator and navigate to Help > About Oracle Applications, or query SELECT release_name FROM apps.fnd_product_groups WHERE release_name LIKE '12.2%'; to obtain the version numberAffected if The installed version falls within 12.2.3 through 12.2.15, the system may be affected
-
Verify Quality Management module is accessibleCheck if the Quality Management Specs function is accessible to users. In EBS, verify through Security > Responsibility > Define and look for Quality Management responsibilities, or check if users have access to the /QA/ spec screensAffected if Quality Management module is enabled and accessible to authenticated users, the SQL injection attack surface exists
-
Confirm HTTP access to EBS is enabledCheck if EBS web interfaces (OA/html or JSP URLs) are exposed. Review Oracle WebLogic/Apache configuration files for EBS ports (typically 8000-8005) and URL patterns like /OA_HTML/ or /forms/frmservletAffected if HTTP/HTTPS access to EBS is enabled, the attack vector is available to remote authenticated users
If Oracle Process Manufacturing Product Development version 12.2.3-12.2.15 is installed with Quality Management module accessible via HTTP to authenticated users, the environment is vulnerable to CVE-2026-46916.
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 Critical Patch Update (CPU) for the affected versions 12.2.3-12.2.15. Restrict network access to Oracle EBS interfaces and implement principle of least privilege for Quality Management module users.
- Consultation6.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 $8,256.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46916 — 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-46916 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