CVE-2026-34309
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 PeopleTools product of Oracle PeopleSoft (component: Security). Supported versions that are affected are 8.61-8.62. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise PeopleSoft Enterprise PeopleTools. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all PeopleSoft Enterprise PeopleTools accessible data as well as unauthorized access to critical data or complete access to all PeopleSoft Enterprise PeopleTools accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 · moderate confidenceA vulnerability in the Security component of Oracle PeopleSoft Enterprise PeopleTools (versions 8.61-8.62) allows a low-privileged attacker with network access via HTTP to perform unauthorized creation, deletion, or modification of critical data, as well as gain unauthorized access to critical or all accessible data within the PeopleSoft environment.
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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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.
-
Confirm PeopleSoft Enterprise PeopleTools installationQuery the PSVERSION table via SQL: SELECT OBJECTTYPE, VERSION FROM PSVERSION WHERE OBJECTTYPE LIKE 'PT%' or check PeopleSoft banner page accessible via HTTPAffected if Oracle PeopleSoft Enterprise PeopleTools is installed
-
Identify installed PeopleTools versionRun SQL query against PSVERSION table or check the PeopleSoft About page (PeopleTools > About) to determine exact version numberAffected if Installed version is exactly 8.61 or 8.62
-
Verify HTTP interface is accessibleCheck if PeopleSoft Internet Architecture (PIA) web servers are reachable via HTTP/HTTPS on standard ports (typically 80, 443, or custom ports)Affected if HTTP/HTTPS interface is exposed to network
-
Confirm Security component is in useVerify the Security component (PeopleTools > Security) is configured and accessible, as this is the vulnerable componentAffected if Security component is enabled and accessible
System is affected if it runs PeopleSoft Enterprise PeopleTools version 8.61 or 8.62 with the Security component accessible via HTTP to low-privileged users
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 PeopleTools. Until patches can be applied, restrict network access to PeopleSoft HTTP interfaces to trusted sources only and enforce additional authentication controls.
Latest available PeopleSoft Enterprise PeopleTools 8.6x release (contact Oracle Support for exact version)
- 1. Identify the current PeopleSoft Enterprise PeopleTools version in use (8.61 or 8.62)
- 2. Navigate to Oracle's official PeopleSoft Enterprise PeopleTools documentation or Oracle Support
- 3. Locate and download the latest Oracle Critical Patch Update (CPU) that addresses CVE-2026-34309
- 4. Review the patch pre-requisites and requirements in the patch readme
- 5. Apply the security patch in a non-production environment first to validate compatibility
- 6. Create a complete backup of the PeopleTools environment before applying the patch
- 7. Apply the patch following Oracle's standard patch application procedures
- 8. Verify the patch was applied successfully by checking the PeopleTools version and security configuration
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $9,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34309 — 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-34309 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