dbcve.org
Peoplesoft Enterprise Pt PeopletoolsApplication · Oracle

CVE-2026-35278

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 PeopleSoft Enterprise PT PeopleTools product of Oracle PeopleSoft (component: Performance Monitor). 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 PT PeopleTools. Successful attacks of this vulnerability can result in takeover of PeopleSoft Enterprise PT PeopleTools. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/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

Critical unauthenticated remote code execution vulnerability in Oracle PeopleSoft Enterprise PT PeopleTools Performance Monitor component affecting versions 8.61 and 8.62. Attackers with network access via HTTP can exploit this easily exploitable flaw to achieve complete system takeover with high impact on confidentiality, integrity, and availability.

MitigationApply Oracle's critical patch for PeopleTools 8.61/8.62 immediately. If patching is not feasible, restrict network access to Performance Monitor endpoints and implement additional authentication layers.

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
Peoplesoft Enterprise Pt 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 the installed PeopleTools version
    Log into PeopleSoft Application Designer or check the PSVERSION table in the database. Query: SELECT * FROM PSVERSION WHERE OBJECTTYPENAME = 'PT_ tools'. Alternatively, check the About PeopleSoft page in the Pure Internet Architecture.
    Affected if The version listed is 8.61 or 8.62
  2. Verify Performance Monitor component is enabled
    Check the PeopleTools Performance Monitor configuration. In the PIA, navigate to PeopleTools > Performance Monitor > System Settings or check the PSTREENODE table for Performance Monitor related nodes. Also verify the Performance Monitor service is running via the WebLogic admin console.
    Affected if Performance Monitor is enabled and the service is running
  3. Confirm Performance Monitor endpoints are network accessible
    Test HTTP access to the Performance Monitor URLs. Common paths include /psp/ps/EMPLOYEE/PT_PM/ and /PerformanceMonitor/. Use a browser or curl to attempt access from an untrusted network location.
    Affected if The Performance Monitor URLs respond without authentication from external networks
  4. Check for unauthenticated access to Performance Monitor
    Review the web server configuration (OHS or WebLogic) for the Performance Monitor application. Verify whether the /PT_PM/ servlet requires authentication or if anonymous access is permitted in the web.xml deployment descriptor.
    Affected if Anonymous or unauthenticated users can access the Performance Monitor servlet or service endpoints

You are affected if PeopleTools version is 8.61 or 8.62 AND the Performance Monitor component is enabled and accessible over the network without authentication.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle's critical patch for PeopleTools 8.61/8.62 immediately. If patching is not feasible, restrict network access to Performance Monitor endpoints and implement additional authentication layers.

Fix this in Peoplesoft Enterprise Pt Peopletools Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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