dbcve.org
Peoplesoft Enterprise PeopletoolsApplication · Oracle

CVE-2026-47026

HIGH · 7.4 CVSS v3.1 Developing Published 2026-07-21
No fix yet
No fix has been published. The vendor has not shipped a fixed release or patch. You remain exposed.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges 4 weeks old

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 PeopleSoft Enterprise PeopleTools product of Oracle PeopleSoft (component: OpenSearch Dashboards). Supported versions that are affected are 8.61 and 8.62. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise PeopleTools. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in PeopleSoft Enterprise PeopleTools, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all PeopleSoft Enterprise PeopleTools accessible data. CVSS 3.1 Base Score 7.4 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-04.

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
Peoplesoft Enterprise PeopletoolsApplication
Affected:= 8.61= 8.62

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

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
Recommended fix Moderate confidence

Apply the Oracle Critical Patch Update that addresses CVE-2026-47026 (check Oracle Support for the specific fixed version for 8.61/8.62)

  1. 1. Review the Oracle Critical Patch Update advisory for PeopleSoft Enterprise PeopleTools for the relevant CPU (likely April 2026 or later).
  2. 2. Navigate to Oracle's official support portal and locate the security patch for CVE-2026-47026.
  3. 3. Download the appropriate patch for your specific version (8.61 or 8.62).
  4. 4. Apply the patch following Oracle's standard patching procedures for PeopleSoft Enterprise PeopleTools.
  5. 5. After patching, verify the OpenSearch Dashboards component is properly updated and restart affected services.
  6. 6. Test that PeopleSoft applications function normally post-patch.
Caveat Oracle CPU patches are generally cumulative; review patch readme for any specific upgrade considerations or prerequisites

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

No vendor fix exists Peoplesoft Enterprise Peopletools has not published a patch for this.

There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.

Add your voice

Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.

Can’t wait

We develop and verify an original fix where the vendor hasn’t, from $1,250. Deployed to your staging first — never straight to production.

Scope it with us

See what else the community needs solved on the solutions-needed board.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47026 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-47026 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