CVE-2026-35289
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 PeopleSoft Enterprise PT PeopleTools product of Oracle PeopleSoft (component: Deployment Package). Supported versions that are affected are 8.61 and 8.62. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTPS 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 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/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 confidenceUnauthenticated remote code execution vulnerability in the Deployment Package component of PeopleSoft Enterprise PT PeopleTools versions 8.61 and 8.62. Despite the 'difficult to exploit' classification, an unauthenticated attacker with network access via HTTPS can achieve complete system compromise (full confidentiality, integrity, and availability impact).
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= 8.61= 8.62CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify PeopleTools installationLocate the PeopleSoft installation and identify the PeopleTools version. This is typically found in the PS_HOME directory or via the PeopleSoft Configuration Manager. Common locations include checking the version.txt file in the installation directory or using the psadmin utility if available.Affected if The installed PeopleTools version is exactly 8.61 or 8.62
-
Verify the Deployment Package componentDetermine if the Deployment Package component (sometimes referred to as Deployment Manager or related packaging features) is configured or enabled in the PeopleSoft environment. This component is part of the PeopleTools infrastructure.Affected if The Deployment Package component is present and active in the environment
-
Assess network exposure of HTTPS interfacesReview firewall rules, network configuration, and access controls around the PeopleSoft HTTPS web endpoints. Identify whether the PeopleSoft services are exposed to untrusted networks.Affected if The PeopleSoft HTTPS interfaces are accessible from untrusted networks or the internet without proper network segmentation
-
Check for unauthenticated access pathwaysEvaluate whether the Deployment Package functionality is accessible without authentication. The vulnerability specifically allows unauthenticated attackers to exploit this component.Affected if Unauthenticated access to the Deployment Package component is possible over HTTPS
A system is affected if it runs PeopleTools version 8.61 or 8.62 with the Deployment Package component enabled and accessible over HTTPS to untrusted networks.
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's available security patches for PeopleSoft Enterprise PT PeopleTools immediately. Until patched, restrict network access to PeopleSoft HTTPS interfaces using network segmentation and firewall rules to limit exposure to trusted sources only.
Upgrade to the latest available PeopleTools version (8.63 or later) that includes the security fix for this vulnerability
- Check the current PeopleTools version by navigating to PeopleTools > Utilities > About PeopleTools
- Review Oracle's Critical Patch Updates for the applicable security fix (Oracle CPUs address this vulnerability quarterly)
- Obtain and apply the latest Oracle Critical Patch Update that addresses CVE-2026-35289
- After applying the patch, verify the Deployment Package component is properly secured
- Confirm the fix by testing authentication requirements for the Deployment Package interface
- Validate that unauthenticated access is no longer possible via HTTPS to the Deployment Package component
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35289 — 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-35289 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