CVE-2026-35271
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: Weblogic). Supported versions that are affected are 8.61 and 8.62. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise PT PeopleTools. While the vulnerability is in PeopleSoft Enterprise PT PeopleTools, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all PeopleSoft Enterprise PT PeopleTools accessible data as well as unauthorized access to critical data or complete access to all PeopleSoft Enterprise PT PeopleTools accessible data. CVSS 3.1 Base Score 8.7 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/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 · high confidenceThis is an unauthenticated HTTP vulnerability in the Weblogic component of PeopleSoft Enterprise PT PeopleTools versions 8.61 and 8.62. An attacker with network access can exploit this to create, modify, or delete critical data, or gain unauthorized access to sensitive information, with potential scope expansion to affect additional products.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
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 PeopleSoft PeopleTools installation and versionLocate the PeopleTools installation directory and check the version. On Windows, check the registry key HKLM\SOFTWARE\PeopleSoft or look for psadmin utility. On Unix/Linux, check common paths like /opt/psft/ or examine the PS_HOME environment variable. Run 'psadmin -v' or check version.properties in the installation directory.Affected if The installed version is exactly 8.61 or 8.62
-
Confirm Weblogic HTTP listener is enabledIdentify the Weblogic port used by PeopleSoft (commonly 7001, 7002, or 8080). Check the Weblogic configuration files (config.xml) or the Weblogic Administration Console to verify HTTP is enabled on the affected instance.Affected if HTTP is enabled on the Weblogic Server listening port (typically port 7001 or similar)
-
Verify network accessibility to Weblogic portCheck if the Weblogic HTTP port (identified in step 2) is accessible from untrusted networks. Review firewall rules, load balancer configurations, and network ACLs to determine if an unauthenticated attacker could reach the HTTP endpoint.Affected if The Weblogic HTTP port is reachable from network segments accessible to untrusted users
You are affected if PeopleTools version is exactly 8.61 or 8.62 AND the Weblogic HTTP listener is exposed to untrusted network access.
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 the relevant Oracle Critical Patch Update for PeopleSoft Enterprise PT PeopleTools that addresses this Weblogic vulnerability, or implement Weblogic-specific security configurations and restrict HTTP access to trusted sources if patches cannot be immediately applied.
Apply Oracle CPU patch for PeopleSoft PeopleTools 8.61/8.62 (contact Oracle for exact fixed version number)
- Check Oracle's Critical Patch Update (CPU) advisory for CVE-2026-35271 at oracle.com for the specific patch number and fixed version
- Apply the latest PeopleSoft Enterprise PT PeopleTools patch from Oracle's CPU for your version (8.61 or 8.62)
- After patching, verify the Weblogic component is updated and restart PeopleSoft services
- Confirm the patch was applied successfully by reviewing the Oracle Opatch output
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35271 — 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-35271 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