CVE-2026-34269
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: Portal). Supported versions that are affected are 8.61-8.62. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise PeopleTools. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in PeopleSoft Enterprise PeopleTools, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of PeopleSoft Enterprise PeopleTools accessible data as well as unauthorized read access to a subset of PeopleSoft Enterprise PeopleTools accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 confidenceA vulnerability in the PeopleSoft Enterprise PeopleTools Portal component (versions 8.61-8.62) allows unauthenticated remote attackers via HTTP to achieve partial read and write access to accessible data. The attack requires human interaction and may impact additional products due to scope change.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 the installed PeopleTools versionQuery the PeopleSoft system for the PeopleTools version using SQL against the PSVERSION table or check the About PeopleSoft page in the Portal. Look for a version string matching 8.61 or 8.62.Affected if The installed PeopleTools version is exactly 8.61 or 8.62.
-
Verify the Portal component is enabledCheck the PeopleSoft Portal configuration to confirm the Portal servlet or IB servlets are active. In the PIA (PeopleSoft Internet Architecture), navigate to PeopleTools > Portal > Portal Utilities > Diagnostics to verify portal status.Affected if The Portal component is configured and accessible via HTTP.
-
Confirm HTTP accessibility of the PortalAttempt to access the PeopleSoft Portal login page over HTTP/HTTPS from an external or untrusted network interface. Check if the /psc/ and /psp/ servlet paths respond without authentication.Affected if The Portal login page or servlets are reachable over HTTP from untrusted networks.
-
Check for lack of network restrictionsReview firewall rules, load balancer ACLs, or network segmentation around the PeopleSoft web servers. Determine if the Portal URLs are exposed to the internet or untrusted internal segments.Affected if No IP-based access restrictions or network segmentation is applied to the Portal endpoints.
A user is affected if their PeopleSoft Enterprise PeopleTools is exactly version 8.61 or 8.62 AND the Portal component is accessible over HTTP without proper network restrictions.
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 latest PeopleSoft Enterprise PeopleTools patch when available. Until then, restrict network access to the Portal to trusted users only and implement WAF rules to detect/abort malicious HTTP requests.
Contact Oracle for latest PeopleTools 8.62.x release with security fixes (or wait for next CPU)
- Contact Oracle Support to obtain the specific Critical Patch Update (CPU) that addresses CVE-2026-34269 for PeopleSoft Enterprise PeopleTools
- Apply the Oracle CPU following Oracle's standard patching procedures for PeopleSoft systems
- After patching, verify the Portal component access controls have been properly remediated
- Test that the PeopleSoft Portal functionality operates correctly post-patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34269 — 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-34269 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