CVE-2026-35276
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: Application Server). 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. 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 · moderate confidenceVulnerability in Oracle PeopleSoft Enterprise PT PeopleTools Application Server allows unauthenticated remote attackers with network access via HTTP to potentially take over the system. The attack is marked as difficult to exploit (high attack complexity) but achieves complete confidentiality, integrity, and availability impact, affecting versions 8.61 and 8.62.
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 PeopleSoft PeopleTools versionAccess the PeopleSoft sign-in page or check the version information in the PeopleSoft Enterprise Manager. The version is typically displayed on the login page or can be retrieved via the PS_HOME version files.Affected if The installed version matches 8.61 or 8.62 exactly.
-
Confirm Application Server component is deployedVerify that the PeopleSoft Application Server (PSAPPSRV) process is running and listening for HTTP requests. Check if the PSAPPSRV.WIN and related configuration files exist in the PS_HOME\appserv directory.Affected if The Application Server component is active and configured to accept HTTP connections.
-
Determine if HTTP listener is enabled on Application ServerExamine the Application Server configuration (psappsrv.cfg) for HTTP listener settings. Look for EnableWebLogic, HttpServer, or similar HTTP enablement flags in the [Interface] or [Http_LISTENER] sections of the config file.Affected if HTTP listeners are enabled and the server is configured to accept unauthenticated HTTP requests.
-
Verify network exposure of the Application ServerReview firewall rules and network segmentation around the PeopleSoft Application Server. Check which network interfaces and IP addresses the PSAPPSRV process is bound to, and whether it is reachable from untrusted networks.Affected if The Application Server HTTP port (typically 80 or 8080) is accessible from untrusted network segments or the public internet.
-
Check for existing Oracle security patchesReview installed Oracle Critical Patch Updates (CPUs) or PeopleSoft-specific patches applied to the system. Cross-reference with Oracle's security advisory documentation.Affected if No Oracle security patch addressing CVE-2026-35276 has been applied to the system.
A user is affected if they are running PeopleTools version 8.61 or 8.62 with the Application Server HTTP listener enabled and accessible from untrusted networks without having applied the relevant Oracle security patch.
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 security patches for PeopleSoft Enterprise PT PeopleTools when released; in the interim, restrict network access to the Application Server to trusted sources only.
PeopleSoft Enterprise PT PeopleTools 8.63 or later
- Check Oracle's Critical Patch Updates for CVE-2026-35276 to obtain the specific patch or fixed version
- If a patch is available from Oracle, apply it according to Oracle's installation instructions
- If no patch is available, upgrade PeopleSoft Enterprise PT PeopleTools to a version newer than 8.62 (such as 8.63 or later) which should contain the fix
- After applying the patch or upgrade, verify that the Application Server now requires proper authentication
- Restrict network access to the PeopleSoft Application Server to trusted networks only as an additional mitigation until the patch/upgrade is applied
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-35276 — 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-35276 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