Hr IntelligenceApplication · Oracle

CVE-2026-46922

HIGH · 7.2 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to after 12.2.15 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Vulnerability in the Oracle HR Intelligence 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 high privileged attacker with network access via HTTP to compromise Oracle HR Intelligence. Successful attacks of this vulnerability can result in takeover of Oracle HR Intelligence. CVSS 3.1 Base Score 7.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/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 confidence

This is a vulnerability in Oracle HR Intelligence (part of Oracle E-Business Suite) affecting the Internal Operations component. It is exploitable via HTTP by high-privileged attackers and allows complete compromise (takeover) of the affected Oracle HR Intelligence system, with high impact on confidentiality, integrity, and availability.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for Oracle E-Business Suite that addresses this vulnerability. Since the attacker requires high privileges, also audit and restrict privileged user accounts and monitor for suspicious administrative activity.

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
Hr IntelligenceApplication
Affected:>= 12.2.3, <= 12.2.15

CVSS 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle HR Intelligence installation
    Locate the Oracle E-Business Suite installation and identify if the HR Intelligence module is deployed. Check the Oracle ApplicationsManager or similar Oracle management console for installed modules.
    Affected if HR Intelligence module is not present in the environment
  2. Determine HR Intelligence version
    Query the Oracle database or use Oracle Application Manager (OAM) to retrieve the HR Intelligence version number. Common methods include querying the version tables or checking the Oracle E-Business Suite version information screen.
    Affected if Installed version falls within 12.2.3 to 12.2.15 inclusive
  3. Verify Internal Operations component
    Check if the Internal Operations component of Oracle HR Intelligence is configured and accessible. This is typically managed through the Oracle Applications Framework (OAF) or Oracle HRMS responsibilities.
    Affected if Internal Operations component is enabled and accessible via the web interface
  4. Confirm HTTP accessibility
    Verify that the Oracle E-Business Suite web interfaces (OA_HTML/OA.jsp) are exposed over HTTP/HTTPS. Check the Oracle HTTP Server configuration and the URLs used to access HR Intelligence.
    Affected if HR Intelligence is accessible via HTTP (not restricted to internal networks or VPN only)
  5. Assess privileged access exposure
    Identify accounts with high privileges in Oracle E-Business Suite that have access to HR Intelligence administrative functions. Review Oracle Responsibilities and User accounts that map to HR Intelligence roles.
    Affected if Multiple high-privileged accounts exist with HR Intelligence access and these accounts are accessible over the network

Environment is affected if Oracle HR Intelligence version 12.2.3 through 12.2.15 is installed with the Internal Operations component enabled and accessible via HTTP to high-privileged users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 12.2.15
Interim mitigation

Apply the relevant Oracle Critical Patch Update (CPU) for Oracle E-Business Suite that addresses this vulnerability. Since the attacker requires high privileges, also audit and restrict privileged user accounts and monitor for suspicious administrative activity.

Recommended fix Moderate confidence

Oracle HR Intelligence 12.2.16 or later (or the applicable CPU patch for your current version)

  1. Contact Oracle Support to obtain the specific Critical Patch Update (CPU) or patch number that addresses CVE-2026-46922 for Oracle HR Intelligence
  2. Review the Oracle Critical Patch Update documentation for the quarter that includes the fix to understand prerequisites and patch applicability
  3. Apply the patch in a non-production environment first to validate compatibility with your specific configuration
  4. Back up the Oracle E-Business Suite database and application tier before applying the patch
  5. Apply the patch following Oracle's standard patch application procedures for E-Business Suite
  6. Verify the patch was applied successfully by checking the adphovr.sql output or Oracle Enterprise Manager
  7. Test critical Oracle HR Intelligence functionality to ensure the patch does not negatively impact existing workflows
  8. Deploy to production after successful validation in non-production
Caveat Review Oracle's patch prerequisites and known issues for the specific patch; some patches may require interim steps or have dependencies

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hr Intelligence Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46922 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46922 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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